Triple
T17222041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Guam |
E418008
|
entity |
| Predicate | embarkedTroopsCapacity |
P75729
|
FINISHED |
| Object | approximately 1,800 Marines |
—
|
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: approximately 1,800 Marines | Statement: [USS Guam, embarkedTroopsCapacity, approximately 1,800 Marines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embarkedTroopsCapacity Context triple: [USS Guam, embarkedTroopsCapacity, approximately 1,800 Marines]
-
A.
embarkedForcesCapacity
chosen
Indicates the maximum number of forces (e.g., troops or personnel) that can be embarked or carried by a given platform or unit.
-
B.
soldiersCapacity
Indicates the maximum number of soldiers that an entity can hold, support, or accommodate.
-
C.
paratroopCapacity
Indicates the maximum number of paratroopers or amount of airborne troops that something (typically a vehicle or vessel) is capable of carrying or deploying.
-
D.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
-
E.
canCarryTroops
Indicates that an entity has the capability to transport troops from one location to another.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dde78f881908b03105fa0298ae2 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.