Triple
T64283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Belgium |
E1277
|
entity |
| Predicate | compartment |
P3722
|
FINISHED |
| Object | palm branches |
—
|
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: palm branches | Statement: [Coat of arms of Belgium, compartment, palm branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compartment Context triple: [Coat of arms of Belgium, compartment, palm branches]
-
A.
chamberInvolved
Indicates that a particular chamber (e.g., legislative or judicial body) participates in, is affected by, or plays a role in the referenced event, process, or relationship.
-
B.
numberOfChambers
Indicates the count of distinct chambers or compartments associated with an entity.
-
C.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
D.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
E.
department
Indicates that one entity functions as an organizational unit or division within another, typically larger, entity.
- F. None of above. chosen
Provenance (4 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.