Triple
T1392583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padma Lakshmi |
E29992
|
entity |
| Predicate | hasNotableScar |
P3816
|
FINISHED |
| Object | right arm |
—
|
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: right arm | Statement: [Padma Lakshmi, hasNotableScar, right arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableScar Context triple: [Padma Lakshmi, hasNotableScar, right arm]
-
A.
hasInjuries
chosen
Indicates that an entity has sustained one or more physical or bodily injuries.
-
B.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
C.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
D.
hasLie
Indicates that an entity is associated with or responsible for a specific lie or false statement.
-
E.
hasNotableIncident
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c360a7f08190ab7e903764b06fdf |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.