Triple
T1021358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCPON |
E22045
|
entity |
| Predicate | hasCollarDevice |
P8783
|
FINISHED |
| Object | gold fouled anchor with three silver stars |
—
|
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 fouled anchor with three silver stars | Statement: [MCPON, hasCollarDevice, gold fouled anchor with three silver stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollarDevice Context triple: [MCPON, hasCollarDevice, gold fouled anchor with three silver stars]
-
A.
wearerDevice
chosen
Indicates that a device is worn or carried by a particular entity (the wearer).
-
B.
individualWearAuthorized
Indicates that an individual is wearing an item or equipment for which they have proper authorization.
-
C.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
D.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
E.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7dd76b081909ed4d2f7adb6480d |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b724c7908190a5b92a57fbdbff4e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.