Triple
T9092095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratapgarh State |
E217913
|
entity |
| Predicate | integratedAfter |
P87127
|
FINISHED |
| Object | Indian independence |
—
|
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: Indian independence | Statement: [Pratapgarh State, integratedAfter, Indian independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedAfter Context triple: [Pratapgarh State, integratedAfter, Indian independence]
-
A.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
-
B.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
C.
integratedFrom
Indicates that something has been formed or constructed by combining or incorporating elements originating from another source.
-
D.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
E.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b18b24819097b525ddad3a85c0 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:14 p.m.