Triple
T7085388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Tiger reserve |
E165060
|
entity |
| Predicate | managementActivity |
P25513
|
FINISHED |
| Object | tiger census |
—
|
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: tiger census | Statement: [Project Tiger reserve, managementActivity, tiger census]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementActivity Context triple: [Project Tiger reserve, managementActivity, tiger census]
-
A.
managedAct
chosen
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
managementIncludes
Indicates that a management entity encompasses, oversees, or has responsibility for the included entity or entities.
-
D.
activeAsManager
Indicates that an entity currently holds and performs the role or responsibilities of a manager in relation to another entity.
-
E.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e511535c819098f60de54930380f |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.