Triple
T29683631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementary |
E751022
|
entity |
| Predicate | leadCharacterCondition |
P46003
|
FINISHED |
| Object | recovering drug addict |
—
|
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: recovering drug addict | Statement: [Elementary, leadCharacterCondition, recovering drug addict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterCondition Context triple: [Elementary, leadCharacterCondition, recovering drug addict]
-
A.
leadCharacterField
Indicates that one entity serves as the primary or main character associated with another entity, such as a work or production.
-
B.
leadCharacterStatus
chosen
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
maleLeadCharacterCondition
Indicates that a specified condition or attribute applies to the male lead character in a narrative or work.
-
D.
leadCharacterCaste
Indicates that the lead character in a work belongs to a specified caste.
-
E.
ledByCharacter
Indicates that an event, group, or activity is directed or guided by a specific character.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6728d8d8881909cc97dd523866934 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:12 p.m.