Triple
T30184835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libyan municipal system |
E767306
|
entity |
| Predicate | definesUnitType |
P191215
|
FINISHED |
| Object | municipality in Libya |
—
|
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: municipality in Libya | Statement: [Libyan municipal system, definesUnitType, municipality in Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesUnitType Context triple: [Libyan municipal system, definesUnitType, municipality in Libya]
-
A.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
B.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
C.
unitTypes
chosen
Indicates that there is a relationship specifying the types or categories of units associated with an entity.
-
D.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
E.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 29, 2026, 7:27 p.m.