Triple
T16800939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Orange |
E408349
|
entity |
| Predicate | isChosenFor |
P118652
|
FINISHED |
| Object | visibility in maritime environments |
—
|
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: visibility in maritime environments | Statement: [International Orange, isChosenFor, visibility in maritime environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChosenFor Context triple: [International Orange, isChosenFor, visibility in maritime environments]
-
A.
symbolicallyChosenFor
chosen
Indicates that an entity has been selected to represent or stand in for something else in a symbolic or emblematic way.
-
B.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
C.
nameChosenToBe
Indicates that an entity has been given or selected to have a particular name.
-
D.
choseToRepresent
Indicates that one entity voluntarily decided to act on behalf of, or serve as a representative for, another entity or cause.
-
E.
madeChoiceBetween
Indicates that an entity selected one option from among two or more specified alternatives.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c826808190aa0a5bfcde2e49a8 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.