Triple
T33727525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Real Transported Man |
E864183
|
entity |
| Predicate | methodComparedTo |
P178109
|
FINISHED |
| Object | Borden’s Transported Man |
—
|
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: Borden’s Transported Man | Statement: [The Real Transported Man, methodComparedTo, Borden’s Transported Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodComparedTo Context triple: [The Real Transported Man, methodComparedTo, Borden’s Transported Man]
-
A.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
B.
comparisonMethod
Indicates the method or criteria used to compare two or more entities or values.
-
C.
hasComparison
Indicates that one entity is being evaluated or contrasted relative to another entity based on some shared attribute or criterion.
-
D.
sometimesComparedTo
Indicates that one entity is occasionally likened or contrasted to another, but not consistently or universally.
-
E.
comparedToPredecessor
Indicates that something is being evaluated or measured in relation to the thing that came immediately before it.
- 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_69f3498a64cc8190b4b414c67b280d93 |
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:44 a.m.