Triple
T36493452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington-class aircraft carrier |
E899113
|
entity |
| Predicate | numberOfUnitsCompletedAsCarriers |
P204899
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Lexington-class aircraft carrier, numberOfUnitsCompletedAsCarriers, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfUnitsCompletedAsCarriers Context triple: [Lexington-class aircraft carrier, numberOfUnitsCompletedAsCarriers, 2]
-
A.
numberOfUnitsCommanded
Indicates the quantity of units that an entity is in command of within a given context.
-
B.
numberOfSuccessfulMissions
Indicates the count of missions that have been completed successfully by the referenced entity or within the specified context.
-
C.
canCarryTroops
Indicates that an entity has the capability to transport troops from one location to another.
-
D.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
-
E.
numberOfBattleshipsCompleted
Indicates the total count of battleships that have been fully constructed or completed.
- F. None of above. chosen
Provenance (4 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.