Triple
T8230872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortes Gerais |
E192288
|
entity |
| Predicate | hasTypeOfBody |
P16808
|
FINISHED |
| Object | consultative assembly |
—
|
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: consultative assembly | Statement: [Cortes Gerais, hasTypeOfBody, consultative assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfBody Context triple: [Cortes Gerais, hasTypeOfBody, consultative assembly]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
typeOfBody
Indicates that one entity is the classification or kind of physical body that the other entity is.
-
C.
includesTypeOfBody
Indicates that one entity encompasses or contains another entity classified as a specific type of body (e.g., physical, celestial, or organizational body).
-
D.
hasSupportBody
Indicates that one entity serves as a supporting structure or body for another entity.
-
E.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78035b488190bfd6b6c5d7b7c002 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.