Triple
T4687507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | economic affairs ministry |
E103955
|
entity |
| Predicate | typicalSubordinateUnit |
P28620
|
FINISHED |
| Object | department of industry |
—
|
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: department of industry | Statement: [economic affairs ministry, typicalSubordinateUnit, department of industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubordinateUnit Context triple: [economic affairs ministry, typicalSubordinateUnit, department of industry]
-
A.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
B.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
C.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
-
D.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
E.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.