Triple
T15942819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linguistic Survey of India |
E386607
|
entity |
| Predicate | conductedDuring |
P3824
|
FINISHED |
| Object | British colonial period |
—
|
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: British colonial period | Statement: [Linguistic Survey of India, conductedDuring, British colonial period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductedDuring Context triple: [Linguistic Survey of India, conductedDuring, British colonial period]
-
A.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
B.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
C.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
D.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
E.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.