Triple
T12331101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duelo a garrotazos |
E293960
|
entity |
| Predicate | positionInHouse |
P81567
|
FINISHED |
| Object | ground floor wall |
—
|
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: ground floor wall | Statement: [Duelo a garrotazos, positionInHouse, ground floor wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInHouse Context triple: [Duelo a garrotazos, positionInHouse, ground floor wall]
-
A.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
B.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
C.
statusInHouse
chosen
Indicates the specific role, position, or standing an entity holds within a particular house or household.
-
D.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
-
E.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f634ee08190b4f533505d402219 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.