Triple
T13703949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Intrepid |
E328589
|
entity |
| Predicate | crewSizeOnFinalMission |
P883
|
FINISHED |
| Object | approximately 13 |
—
|
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 13 | Statement: [USS Intrepid, crewSizeOnFinalMission, approximately 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewSizeOnFinalMission Context triple: [USS Intrepid, crewSizeOnFinalMission, approximately 13]
-
A.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
B.
crewCountApproximate
chosen
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
C.
totalCrewMembers
Indicates the total number of crew members associated with a given entity or context.
-
D.
squadronSize
Indicates the number of units or members that make up a particular squadron.
-
E.
crewRequired
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad162158819089280ee1e6b5c2cf |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.