Triple
T33461489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John McIntyre (real-life surgeon) |
E856927
|
entity |
| Predicate | hasPersonaUsedIn |
P194954
|
FINISHED |
| Object | M*A*S*H novels |
—
|
NE NERFINISHED |
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: M*A*S*H novels | Statement: [John McIntyre (real-life surgeon), hasPersonaUsedIn, M*A*S*H novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonaUsedIn Context triple: [John McIntyre (real-life surgeon), hasPersonaUsedIn, M*A*S*H novels]
-
A.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
B.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
D.
hasPerformedAs
Indicates that one entity has taken on or executed a particular role, character, or performance associated with another entity.
-
E.
hasPerson
Indicates that an entity is associated with or includes a specific person.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: May 1, 2026, 1:37 a.m.