Triple
T5381632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRF11 |
E113096
|
entity |
| Predicate | spatialUnitType |
P63660
|
FINISHED |
| Object | territorial unit for statistics |
—
|
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: territorial unit for statistics | Statement: [FRF11, spatialUnitType, territorial unit for statistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spatialUnitType Context triple: [FRF11, spatialUnitType, territorial unit for statistics]
-
A.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
B.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
C.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
D.
samplingUnit
Indicates that one entity serves as the basic unit or element from which samples are drawn or measured in a sampling process.
-
E.
managementUnitOf
Indicates that one entity serves as the administrative or managerial unit responsible for overseeing or controlling another entity.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:03 p.m.