Triple
T248779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine One |
E5095
|
entity |
| Predicate | typicalFormationSize |
P3668
|
FINISHED |
| Object | multiple identical helicopters for security |
—
|
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: multiple identical helicopters for security | Statement: [Marine One, typicalFormationSize, multiple identical helicopters for security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFormationSize Context triple: [Marine One, typicalFormationSize, multiple identical helicopters for security]
-
A.
typicalTeamSize
chosen
Indicates the usual or most common number of members that make up a given team.
-
B.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
C.
typicalTeamDesignation
Indicates the standard or commonly used team name or label that is typically assigned to an entity.
-
D.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.