Triple
T16809898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurence Tureaud |
E408578
|
entity |
| Predicate | hasSignatureAccessory |
P32620
|
FINISHED |
| Object | gold chains |
—
|
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: gold chains | Statement: [Laurence Tureaud, hasSignatureAccessory, gold chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureAccessory Context triple: [Laurence Tureaud, hasSignatureAccessory, gold chains]
-
A.
hasSignatureEquipment
Indicates that an entity is associated with a distinctive or characteristic piece of equipment that is uniquely or notably linked to it.
-
B.
hasAccessoryType
Indicates that an entity is associated with or characterized by a particular type or category of accessory.
-
C.
hasSignatureMechanic
Indicates that an entity (such as a game, character, or system) possesses a distinctive, defining mechanic or feature that is uniquely characteristic of it.
-
D.
hasSignatureItem
chosen
Indicates that an entity is associated with a distinctive or primary item that characterizes or represents it.
-
E.
hasSignInventory
Indicates that an entity possesses or is associated with a specific set or collection of signs used within a writing or symbolic system.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cf680c8190bcd640570c524918 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.