Triple
T20414608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intrepid-class starship |
E500674
|
entity |
| Predicate | shuttlecraftCapacity |
P74265
|
FINISHED |
| Object | multiple shuttlecraft |
—
|
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: multiple shuttlecraft | Statement: [Intrepid-class starship, shuttlecraftCapacity, multiple shuttlecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shuttlecraftCapacity Context triple: [Intrepid-class starship, shuttlecraftCapacity, multiple shuttlecraft]
-
A.
hasShuttlecraft
chosen
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
-
B.
carriesCrewOf
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
-
C.
hasShuttlecraftType
Indicates that an entity possesses or is associated with a specific type or classification of shuttlecraft.
-
D.
hasShuttleBay
Indicates that an entity possesses or is equipped with a shuttle bay as part of its structure or facilities.
-
E.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a4281048190a2b016ec16b7d203 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.