Triple
T35210447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 America’s Cup |
E1016658
|
entity |
| Predicate | replacedBoatClass |
P34752
|
FINISHED |
| Object | 12-metre class |
—
|
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: 12-metre class | Statement: [1992 America’s Cup, replacedBoatClass, 12-metre class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedBoatClass Context triple: [1992 America’s Cup, replacedBoatClass, 12-metre class]
-
A.
replacedRollingStock
Indicates that one rolling stock asset has been substituted or superseded by another in service or operational use.
-
B.
renamedShipAs
Indicates that one entity changed the name of a ship to another specified name.
-
C.
replacedClass
chosen
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
D.
secondShipRenamedAs
Indicates that a second ship has been given a new name, establishing a renaming relationship between its prior and current identities.
-
E.
notableBoatClass
Indicates that the subject is a notable or significant example of the specified class or type of boat.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:02 p.m.