Triple
T33873366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Oher |
E868283
|
entity |
| Predicate | experiencedHomelessness |
P178119
|
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: [Michael Oher, experiencedHomelessness, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedHomelessness Context triple: [Michael Oher, experiencedHomelessness, true]
-
A.
estimatedHomeless
Indicates that a person or group is assessed or classified as likely experiencing homelessness, typically based on estimation rather than confirmed status.
-
B.
experiencedPersecution
Indicates that one entity has been subjected to hostile or oppressive treatment, often systematic or repeated, by another entity or group.
-
C.
hasNumberOfHomeless
Indicates the quantified count of homeless individuals associated with a given entity or context.
-
D.
allegedlyExperienced
Indicates that an entity is claimed or reported to have undergone or had a particular experience, without asserting that the experience actually occurred.
-
E.
abuseSurvivorOf
Indicates that one entity has previously suffered abuse perpetrated by the other entity.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:47 a.m.