Triple
T625790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Don’t Tread on Me" (associated naval ensign) |
E15814
|
entity |
| Predicate | hasUseContext |
P5018
|
FINISHED |
| Object | naval warfare |
—
|
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: naval warfare | Statement: ["Don’t Tread on Me" (associated naval ensign), hasUseContext, naval warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUseContext Context triple: ["Don’t Tread on Me" (associated naval ensign), hasUseContext, naval warfare]
-
A.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
-
B.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
E.
scopeOfUse
chosen
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.