Triple
T3255662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of Arms of Queensland |
E68287
|
entity |
| Predicate | featuresMalteseCross |
P36674
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Coat of Arms of Queensland, featuresMalteseCross, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMalteseCross Context triple: [Coat of Arms of Queensland, featuresMalteseCross, true]
-
A.
featuresCrossShape
chosen
Indicates that something has a form, pattern, or configuration resembling a cross shape.
-
B.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
-
C.
featuresCrossoverWith
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
D.
crossesIn
Indicates that one entity passes over or through the path, boundary, or area occupied by another entity, intersecting its space or trajectory.
-
E.
collarFeature
Indicates that one entity has a specific characteristic, detail, or attribute related to a collar.
- 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.