Triple
T21089208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLASS |
E519586
|
entity |
| Predicate | intendedBasing |
P17737
|
FINISHED |
| Object | nuclear-powered aircraft carriers |
—
|
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: nuclear-powered aircraft carriers | Statement: [UCLASS, intendedBasing, nuclear-powered aircraft carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBasing Context triple: [UCLASS, intendedBasing, nuclear-powered aircraft carriers]
-
A.
basingConcept
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
B.
potentialBasing
chosen
Indicates a relationship where one entity could serve as the base, foundation, or supporting location for another, but this basing has not yet been realized or confirmed.
-
C.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
D.
basingMode
Indicates the method or principle on which something is founded, justified, or determined.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094dd65481909391ed74115afc23 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.