Triple
T30813351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheya |
E784704
|
entity |
| Predicate | hasPartIncorporatedInto |
P106007
|
FINISHED |
| Object | Gitanjali |
—
|
NE NERFINISHED |
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: Gitanjali | Statement: [Kheya, hasPartIncorporatedInto, Gitanjali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartIncorporatedInto Context triple: [Kheya, hasPartIncorporatedInto, Gitanjali]
-
A.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
B.
partiallyIncorporatedInto
Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
-
C.
elementsIncorporatedInto
chosen
Indicates that one or more elements are taken in and made part of another entity, structure, or system.
-
D.
demergedInto
Indicates that an entity has been split or separated into one or more distinct successor entities as a result of a demerger process.
-
E.
wasRestructuredInto
Indicates that an entity underwent an organizational or structural change resulting in it becoming a different, successor entity.
- F. None of above.
Provenance (3 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: April 29, 2026, 8:43 p.m.