Triple
T30743283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitana |
E782747
|
entity |
| Predicate | relativeImportanceInFleet |
P204201
|
FINISHED |
| Object | principal ship |
—
|
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: principal ship | Statement: [Capitana, relativeImportanceInFleet, principal ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeImportanceInFleet Context triple: [Capitana, relativeImportanceInFleet, principal ship]
-
A.
relativeSizeInFleet
Indicates the comparative size or capacity of an entity relative to other entities within the same fleet.
-
B.
relativeImportanceToTeam2
Indicates the comparative level of importance or value that one entity has relative to another within the context of a team.
-
C.
relativeImportanceToTeam1
Indicates the degree to which something is considered important or valuable to Team 1 relative to other things.
-
D.
relativeImportanceInCountry
Indicates the comparative significance or priority of something within the context of a specific country.
-
E.
relativeImportanceAtAirport
Indicates the comparative level of importance or priority assigned to entities within the context of an airport.
- F. None of above. chosen
Provenance (4 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0346b487088190814e4bd0765cb609 |
completed | May 12, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_6a0346428c60819090e5ea815c0921ca |
completed | May 12, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_6a0346b3b2708190b713ce3dfee1734a |
completed | May 12, 2026, 3:26 p.m. |
Created at: April 29, 2026, 8:38 p.m.