Triple
T9598834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DH |
E231798
|
entity |
| Predicate | associatedWithSubunit |
P66180
|
FINISHED |
| Object | centime |
—
|
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: centime | Statement: [DH, associatedWithSubunit, centime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSubunit Context triple: [DH, associatedWithSubunit, centime]
-
A.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
B.
associatedWithSubdivision
chosen
Indicates that one entity has a connection or linkage to a specific administrative or organizational subdivision.
-
C.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
D.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
E.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3819608190b3c280f5e1845f85 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.