Triple
T2696888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Jaleo |
E58531
|
entity |
| Predicate | foregroundFeature |
P14070
|
FINISHED |
| Object | dancer illuminated by strong light |
—
|
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: dancer illuminated by strong light | Statement: [El Jaleo, foregroundFeature, dancer illuminated by strong light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foregroundFeature Context triple: [El Jaleo, foregroundFeature, dancer illuminated by strong light]
-
A.
frontLineFeature
chosen
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
B.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
C.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
D.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
E.
firstToFeature
Indicates that one entity was the earliest or initial subject to exhibit, include, or present another entity in 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda3112108190a5e49c13368cf83f |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.