Triple
T762871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Gabriel of Belgium |
E16108
|
entity |
| Predicate | monogram |
P16921
|
FINISHED |
| Object | Royal monogram of Prince Gabriel of Belgium |
—
|
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: Royal monogram of Prince Gabriel of Belgium | Statement: [Prince Gabriel of Belgium, monogram, Royal monogram of Prince Gabriel of Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monogram Context triple: [Prince Gabriel of Belgium, monogram, Royal monogram of Prince Gabriel of Belgium]
-
A.
emblemName
chosen
Indicates that a specified name is the official or recognized title of an emblem.
-
B.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
-
C.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
D.
signatureTheme
Indicates that something serves as a distinctive, defining theme strongly associated with a particular entity or context.
-
E.
mottoStyle
Indicates the stylistic form or presentation in which a motto is expressed.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6841f388190a6d08c3bf5c17fe4 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a506106081909ef97a679ff00a5a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.