Triple
T36515242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington-class battlecruiser |
E900016
|
entity |
| Predicate | designFinalized |
P54426
|
FINISHED |
| Object | early 1920s |
—
|
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: early 1920s | Statement: [Lexington-class battlecruiser, designFinalized, early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designFinalized Context triple: [Lexington-class battlecruiser, designFinalized, early 1920s]
-
A.
designCompletion
chosen
Indicates that the design phase of something has been finished or brought to completion.
-
B.
designStatus
Indicates the current state or phase of progress for a design within its lifecycle.
-
C.
designStarted
Indicates that the process of designing something has been initiated or begun.
-
D.
designOutcome
Indicates the result, effect, or consequence produced by a particular design or design process.
-
E.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:10 p.m.