Triple
T9616599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Angel Inn Restaurante |
E232233
|
entity |
| Predicate | romanticAtmosphere |
P62080
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [San Angel Inn Restaurante, romanticAtmosphere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticAtmosphere Context triple: [San Angel Inn Restaurante, romanticAtmosphere, true]
-
A.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
B.
romanticMisunderstandingsWith
Indicates a situation where two entities experience confusion, misinterpretation, or mistaken beliefs about each other’s romantic feelings, intentions, or relationship status.
-
C.
romanticReputation
Indicates how an entity is perceived or regarded by others in the context of romantic behavior, history, or involvement.
-
D.
romanticTriangleInvolves
Indicates a romantic relationship structure in which three individuals are mutually or asymmetrically involved in overlapping romantic connections.
-
E.
featuresMood
chosen
Indicates that something includes, presents, or conveys a particular mood or emotional atmosphere.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aad71a0819084ea00c2409e9922 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.