Triple
T18462666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian regions |
E451076
|
entity |
| Predicate | haveBody |
P131753
|
FINISHED |
| Object | regional council |
—
|
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: regional council | Statement: [Italian regions, haveBody, regional council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveBody Context triple: [Italian regions, haveBody, regional council]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
usesBody
Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
-
C.
hasMainBody
Indicates that one entity serves as the primary physical or structural body of another entity.
-
D.
mayHaveBody
Indicates that an entity is permitted or able to possess a physical or conceptual body.
-
E.
hasSupportBody
Indicates that one entity serves as a supporting structure or body for 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a80a2bc81909ec14811577a311d |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:33 a.m.