Triple
T3462293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Battalion, 7th Marines |
E73052
|
entity |
| Predicate | traditionalSize |
P3664
|
FINISHED |
| Object | approximately 800 Marines and sailors |
—
|
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 800 Marines and sailors | Statement: [3rd Battalion, 7th Marines, traditionalSize, approximately 800 Marines and sailors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSize Context triple: [3rd Battalion, 7th Marines, traditionalSize, approximately 800 Marines and sailors]
-
A.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
B.
typicalUnitSize
chosen
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
C.
typicalCastSize
Indicates the usual or standard number of cast members involved in a production or performance.
-
D.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
E.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae867c4819091c76e63e44290b4 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.