Triple
T32582741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Cross of the Order of Leopold |
E832832
|
entity |
| Predicate | hasStarShape |
P82774
|
FINISHED |
| Object | multi-rayed silver star |
—
|
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: multi-rayed silver star | Statement: [Grand Cross of the Order of Leopold, hasStarShape, multi-rayed silver star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarShape Context triple: [Grand Cross of the Order of Leopold, hasStarShape, multi-rayed silver star]
-
A.
hasMainAsterismShape
Indicates that an entity is associated with a specific primary asterism shape that characterizes its overall pattern or outline.
-
B.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
C.
containsStarType
Indicates that one entity includes or is associated with a star of a specified stellar type.
-
D.
hasStars
Indicates that an entity possesses or is associated with one or more stars.
-
E.
hasDistinctiveShape
chosen
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:04 a.m.