Triple
T3747792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian tricolour naval ensign |
E81248
|
entity |
| Predicate | stripeOrderFromHoist |
P18862
|
FINISHED |
| Object | green white red |
—
|
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: green white red | Statement: [Italian tricolour naval ensign, stripeOrderFromHoist, green white red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stripeOrderFromHoist Context triple: [Italian tricolour naval ensign, stripeOrderFromHoist, green white red]
-
A.
stripeOrder
chosen
Indicates an ordering relationship where one stripe is positioned or sequenced before or after another stripe.
-
B.
orderFoundedFrom
Indicates that an order was initiated or created as a result of, or originating from, a specific source or prior entity.
-
C.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or entity.
-
D.
orderFounded
Indicates that an organization or group was established or created at a specific time or by a specific entity.
-
E.
associatedOrderFoundedIn
Indicates that an order or organization associated with an entity was founded in a specified place or time.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.