Triple
T24365388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | development rights movement |
E614179
|
entity |
| Predicate | prominentlyAdvancedIn |
P51406
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [development rights movement, prominentlyAdvancedIn, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentlyAdvancedIn Context triple: [development rights movement, prominentlyAdvancedIn, India]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
elevatedInProminenceBy
Indicates that an entity’s prominence, status, or visibility is increased as a result of the actions or influence of another entity.
-
C.
adoptedProminentlyBy
chosen
Indicates that something (such as an idea, practice, or technology) has been widely and visibly taken up or embraced by a particular group or entity.
-
D.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
E.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293874f7c8190b472e99640e97f62 |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.