Triple
T16505047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Fighter Attack Squadron |
E400903
|
entity |
| Predicate | canDeployFrom |
P86355
|
FINISHED |
| Object | aircraft carrier |
—
|
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: aircraft carrier | Statement: [Marine Fighter Attack Squadron, canDeployFrom, aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDeployFrom Context triple: [Marine Fighter Attack Squadron, canDeployFrom, aircraft carrier]
-
A.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
-
B.
canDeployWith
Indicates that one entity is compatible or allowed to be deployed together with another entity in the same environment or configuration.
-
C.
canDeployAs
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
D.
canDeployWithin
chosen
Indicates that one entity has the capability or permission to be deployed inside or within the scope, boundary, or environment defined by another entity.
-
E.
canDeployBeyond
Indicates that an entity has the capability or authorization to deploy something to locations or contexts that extend beyond a specified boundary or scope.
- 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.