Triple
T27017564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Liscome Bay |
E680574
|
entity |
| Predicate | classLaidDownAs |
P38948
|
FINISHED |
| Object | escort aircraft carrier |
—
|
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: escort aircraft carrier | Statement: [USS Liscome Bay, classLaidDownAs, escort aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classLaidDownAs Context triple: [USS Liscome Bay, classLaidDownAs, escort aircraft carrier]
-
A.
laidDownAs
chosen
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
-
B.
firstOfClassLaidDown
Indicates that the subject is the very first instance of its class or type to have been established, created, or laid down.
-
C.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
D.
introducedAsPartOfClass
Indicates that something was introduced as a component or element within a particular class or course.
-
E.
laidDownBy
Indicates that something was established, created, or set as a rule, principle, or foundation by a particular agent.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:07 a.m.