Triple
T23648481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Ledbetter |
E584099
|
entity |
| Predicate | typicalLivePosition |
P153028
|
FINISHED |
| Object | show closer |
—
|
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: show closer | Statement: [Yellow Ledbetter, typicalLivePosition, show closer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLivePosition Context triple: [Yellow Ledbetter, typicalLivePosition, show closer]
-
A.
typicalPositionType
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
B.
typicalPositionsInclude
Indicates that certain positions or roles are commonly or characteristically included within something (such as an organization, structure, or context).
-
C.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
-
D.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
E.
targetUserPosition
Indicates the spatial position or location of a specified user relative to a reference frame or environment.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b287606881909926de5efd882a76 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:49 p.m.