Triple
T27938034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Lawrence Gordon |
E700663
|
entity |
| Predicate | chainedBy |
P81670
|
FINISHED |
| Object | ankle chain |
—
|
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: ankle chain | Statement: [Dr. Lawrence Gordon, chainedBy, ankle chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chainedBy Context triple: [Dr. Lawrence Gordon, chainedBy, ankle chain]
-
A.
chainedAt
chosen
Indicates that one entity is physically secured to another (or to a fixed point) using a chain, restricting its movement or separation.
-
B.
hasChainDepicted
Indicates that an entity has a chain (or chains) visually represented as part of its depiction.
-
C.
importedBy
Indicates that one entity brings another entity into a system, context, or location from an external source.
-
D.
compositionallyLinkedTo
Indicates that one entity is connected to another as part of a larger composition, such that changes or properties of one are meaningfully related to the combined whole.
-
E.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
- 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.