Triple
T16505040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Fighter Attack Squadron |
E400903
|
entity |
| Predicate | typicalSupportElement |
P95346
|
FINISHED |
| Object | squadron headquarters |
—
|
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: squadron headquarters | Statement: [Marine Fighter Attack Squadron, typicalSupportElement, squadron headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSupportElement Context triple: [Marine Fighter Attack Squadron, typicalSupportElement, squadron headquarters]
-
A.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
B.
typicalSupportedUnitType
Indicates the kind or category of unit that an entity is normally designed or expected to support.
-
C.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
typicalDesignElement
chosen
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
E.
typicalSupportSeriesRole
Indicates the usual or characteristic role that an entity plays within a support series or sequence of related support activities.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e51ce1c81909548298f703a7ffa |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.