Triple
T791212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Ensign |
E16917
|
entity |
| Predicate | timeInUse |
P13716
|
FINISHED |
| Object | in continuous use in various forms since the 17th century |
—
|
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: in continuous use in various forms since the 17th century | Statement: [White Ensign, timeInUse, in continuous use in various forms since the 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUse Context triple: [White Ensign, timeInUse, in continuous use in various forms since the 17th century]
-
A.
durationOfUse
chosen
Indicates the length of time for which something is used or remains in use.
-
B.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79754988190ab494b1c54d6a2a4 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.