Triple
T3716895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-4 Skyhawk |
E81551
|
entity |
| Predicate | usedByBlueAngelsPeriod |
P51377
|
FINISHED |
| Object | 1974–1986 |
—
|
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: 1974–1986 | Statement: [A-4 Skyhawk, usedByBlueAngelsPeriod, 1974–1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByBlueAngelsPeriod Context triple: [A-4 Skyhawk, usedByBlueAngelsPeriod, 1974–1986]
-
A.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
-
C.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
D.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- F. None of above. chosen
Provenance (4 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9d087c881909f6d2ec6e518fb02 |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc48ec1a081909af0ff9f267c0ffe |
completed | March 8, 2026, 6:48 p.m. |
Created at: March 8, 2026, 3:33 p.m.