Triple
T36987581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemon Drop Kid |
E915004
|
entity |
| Predicate | stoodIn |
P186856
|
FINISHED |
| Object | Kentucky |
—
|
NE NERFINISHED |
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: Kentucky | Statement: [Lemon Drop Kid, stoodIn, Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoodIn Context triple: [Lemon Drop Kid, stoodIn, Kentucky]
-
A.
stoodDown
Indicates that an entity relinquished its active role, position, or state of readiness, often stepping aside from duty or responsibility.
-
B.
standsUpTo
Indicates confronting, resisting, or opposing another entity’s actions, demands, or influence, especially in the face of pressure or intimidation.
-
C.
stands
Indicates that an entity is in an upright position, typically supported by its feet or base, rather than sitting, lying, or moving.
-
D.
standsAt
Indicates that one entity is positioned upright at or near a specific location or reference point associated with another entity.
-
E.
stoodFor
Indicates that one entity represented, supported, or defended another entity, cause, or principle, often in a public or symbolic way.
- F. None of above. chosen
Provenance (4 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.