Triple
T27938044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Lawrence Gordon |
E700663
|
entity |
| Predicate | roleLater |
P138651
|
FINISHED |
| Object | Jigsaw apprentice |
—
|
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: Jigsaw apprentice | Statement: [Dr. Lawrence Gordon, roleLater, Jigsaw apprentice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleLater Context triple: [Dr. Lawrence Gordon, roleLater, Jigsaw apprentice]
-
A.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
B.
subsequentRole
chosen
Indicates that one role or position is held after, and in succession to, another role or position.
-
C.
roleAfterManaging
Indicates the role or position an entity assumes after it has finished managing another entity or activity.
-
D.
roleWhen
Indicates a temporal relationship specifying the time or condition under which a particular role is held or applies.
-
E.
roleAtA24
Indicates that an entity holds or held a specific role or position at the organization or project referred to as A24.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:15 p.m.