Triple
T27955681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (CVN-80) |
E703540
|
entity |
| Predicate | hasNamesakeTradition |
P78011
|
FINISHED |
| Object | eighth U.S. Navy ship named Enterprise |
—
|
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: eighth U.S. Navy ship named Enterprise | Statement: [USS Enterprise (CVN-80), hasNamesakeTradition, eighth U.S. Navy ship named Enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeTradition Context triple: [USS Enterprise (CVN-80), hasNamesakeTradition, eighth U.S. Navy ship named Enterprise]
-
A.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
B.
belongsToNamingTradition
chosen
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
C.
hasNamesakeFamilyName
Indicates that two entities share the same family name, with one serving as the namesake for the other's family name.
-
D.
hasNamesakeRoleInHistory
Indicates that an entity has a historical role or position that is the same as, or named after, another entity’s role in history.
-
E.
hasEarlierNamesake
Indicates that an entity shares its name with another entity that existed earlier in time.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 7:27 p.m.