Triple
T11827229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jataka tales |
E281286
|
entity |
| Predicate | laterCompiledAs |
P101708
|
FINISHED |
| Object | written texts |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: written texts | Statement: [Jataka tales, laterCompiledAs, written texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCompiledAs Context triple: [Jataka tales, laterCompiledAs, written texts]
-
A.
compiledTo
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
B.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
C.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
-
D.
compiledAt
Indicates that one entity was built or transformed into an executable or final form at a specific time or location represented by the other entity.
-
E.
compliedWith
Indicates that one entity has acted in accordance with, or fulfilled the requirements of, another entity’s rules, requests, or standards.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5ec3a148190bb184ba0d481b16a |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.