Triple
T216977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Guard ensign |
E4126
|
entity |
| Predicate | stripeOrientation |
P4984
|
FINISHED |
| Object | vertical |
—
|
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: vertical | Statement: [Coast Guard ensign, stripeOrientation, vertical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stripeOrientation Context triple: [Coast Guard ensign, stripeOrientation, vertical]
-
A.
hasStripeOrientation
chosen
Indicates the directional arrangement or alignment of stripes present on an entity.
-
B.
supportsInternationalOrientation
Indicates that one entity facilitates, promotes, or enables the international focus, outlook, or activities of another entity.
-
C.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
D.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
E.
hasWritingDirection
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c4edfa081909fe97c86c3c7801d |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.