Triple
T34695955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | seal of Sint Maarten |
E891030
|
entity |
| Predicate | centralDesign |
P103764
|
FINISHED |
| Object | coat of arms of Sint Maarten |
—
|
NE NERFINISHED |
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: coat of arms of Sint Maarten | Statement: [seal of Sint Maarten, centralDesign, coat of arms of Sint Maarten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralDesign Context triple: [seal of Sint Maarten, centralDesign, coat of arms of Sint Maarten]
-
A.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
B.
centralProject
Indicates that one project serves as the primary or core project around which other related projects or activities are organized.
-
C.
projectionDesignBy
Indicates that a projection or projected visual element is created or designed by a particular agent or designer.
-
D.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
-
E.
currentDesign
chosen
Indicates that an entity is the presently active or most up-to-date design associated with another entity or context.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 2:05 a.m.