Triple
T3255932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roll of Honour |
E68294
|
entity |
| Predicate | isPhysicalStructure |
P40629
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Roll of Honour, isPhysicalStructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhysicalStructure Context triple: [Roll of Honour, isPhysicalStructure, yes]
-
A.
isPhysicalArtifact
chosen
Indicates that the subject is a tangible, man-made object that physically exists in the real world.
-
B.
hasPhysicalNature
Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
-
C.
physicalBasis
Indicates that one entity serves as the underlying physical foundation, mechanism, or substrate that gives rise to or supports the properties, behavior, or existence of another entity.
-
D.
hasPhysicalFootprint
Indicates that one entity occupies or affects a specific physical area or space in the real world.
-
E.
hasMovementStructure
Indicates that one entity possesses or is characterized by a particular structure or pattern of movement.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf6753b0819081755a529fd87cb1 |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.