Triple
T14608033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcalde |
E342882
|
entity |
| Predicate | headsBody |
P652
|
FINISHED |
| Object | ayuntamiento |
—
|
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: ayuntamiento | Statement: [Alcalde, headsBody, ayuntamiento]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headsBody Context triple: [Alcalde, headsBody, ayuntamiento]
-
A.
heads
chosen
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
B.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
C.
headDescription
Indicates that one entity serves as a textual or semantic description of the head (primary) entity in the relationship.
-
D.
headRegion
Indicates that one entity is the head or primary governing region of another entity.
-
E.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44d327c8190a8d20568429d0f80 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.