Triple
T16804202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Langley |
E408436
|
entity |
| Predicate | previousHullNumber |
P3152
|
FINISHED |
| Object | AC-3 |
E1235683
|
NE 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: AC-3 | Statement: [USS Langley, previousHullNumber, AC-3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AC-3 Context triple: [USS Langley, previousHullNumber, AC-3]
-
A.
AC-3
AC-3 is a multichannel digital audio compression format developed by Dolby Laboratories, widely used for surround sound in cinema, DVD, and broadcast applications.
-
B.
AC-3
chosen
AC-3 was the original hull classification number assigned to USS Langley, the United States Navy’s first aircraft carrier and a pioneering vessel in naval aviation history.
-
C.
ACO
ACO is the commonly used abbreviation for Allied Command Operations, one of NATO’s two strategic military commands responsible for planning and executing alliance operations.
-
D.
ACO
ACO (Automobile Club de l’Ouest) is a French motorsport organization best known as the creator and promoter of the 24 Hours of Le Mans and other major endurance racing events.
-
E.
ACI
ACI is Cisco's software-defined networking solution that provides centralized, policy-based automation and management for data center networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cb68508190a05749bad68f7b43 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb0dce448190b20ca3d60d9fc475 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:22 a.m.