Triple
T8773286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IN-KL |
E208516
|
entity |
| Predicate | hasParentCode |
P85321
|
FINISHED |
| Object | IN |
—
|
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: IN | Statement: [IN-KL, hasParentCode, IN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentCode Context triple: [IN-KL, hasParentCode, IN]
-
A.
hasParentProgram
Indicates that a given program is hierarchically contained within or derived from another, higher-level program that serves as its parent.
-
B.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
C.
hasParentCategory
Indicates that an entity belongs to or is organized under a broader, more general category.
-
D.
hasParentAgencyType
Indicates that an agency is associated with or falls under a parent agency of a specified type.
-
E.
hasParentService
Indicates that one service functions as the parent or higher-level service from which another service is derived, managed, or logically grouped.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:41 p.m.