Triple
T36000143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnum T. A. |
E1041104
|
entity |
| Predicate | inspiredRingNameBy |
P159470
|
FINISHED |
| Object | Tom Selleck’s Magnum, P.I. character |
—
|
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: Tom Selleck’s Magnum, P.I. character | Statement: [Magnum T. A., inspiredRingNameBy, Tom Selleck’s Magnum, P.I. character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredRingNameBy Context triple: [Magnum T. A., inspiredRingNameBy, Tom Selleck’s Magnum, P.I. character]
-
A.
inspiredRingNameOf
chosen
Indicates that one entity’s ring name was inspired by or derived from another entity.
-
B.
motherRingName
Indicates the name of the ring to which a given ring (or sub-ring) is hierarchically related as its “mother” or parent ring.
-
C.
ringName
Indicates that a ring is identified or referred to by a specific name.
-
D.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
E.
shapeInspiredNickname
Indicates that one entity’s physical shape or form served as the inspiration for another entity’s nickname.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:07 p.m.