Triple
T26210271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjuman-e-Khawatin-e-Islam |
E655468
|
entity |
| Predicate | countryAtTimeOfActivity |
P103056
|
FINISHED |
| Object | British India |
E838
|
NE 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 India | Statement: [Anjuman-e-Khawatin-e-Islam, countryAtTimeOfActivity, British India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryAtTimeOfActivity Context triple: [Anjuman-e-Khawatin-e-Islam, countryAtTimeOfActivity, British India]
-
A.
countryAtTheTime
Indicates that an entity is associated with a specific country as it existed at a particular point in time.
-
B.
projectCountryAtTheTime
Indicates the country with which a project was associated at the specific time or period in question.
-
C.
locationCountryAtTheTime
chosen
Indicates that an entity was located in a specified country during a particular time or time period.
-
D.
countryDuring
Indicates that one entity exists, occurs, or is valid within the temporal span during which the other entity is recognized as a specific country.
-
E.
countryOf
Indicates that one entity is the country to which another entity belongs, is located in, or is associated with.
- F. None of above.
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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1185822d388190b3a272f8edf4acb9 |
completed | May 23, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 26, 2026, 8:52 p.m.