Triple
T524070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just Wright |
E10878
|
entity |
| Predicate | leadCharacterOccupation |
P7041
|
FINISHED |
| Object | physical therapist |
—
|
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: physical therapist | Statement: [Just Wright, leadCharacterOccupation, physical therapist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterOccupation Context triple: [Just Wright, leadCharacterOccupation, physical therapist]
-
A.
representedOccupation
Indicates that one entity has served as an official or formal representative of another entity’s occupation or professional role.
-
B.
portraysProfession
chosen
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
-
C.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
D.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b656c08190b387f21b06d99e68 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.