Triple
T32307730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle "E" |
E825411
|
entity |
| Predicate | competitiveCategoriesInclude |
P174395
|
FINISHED |
| Object | surface ships |
—
|
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: surface ships | Statement: [Battle "E", competitiveCategoriesInclude, surface ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveCategoriesInclude Context triple: [Battle "E", competitiveCategoriesInclude, surface ships]
-
A.
competitiveCategory
Indicates that two entities belong to the same market or activity segment in which they compete with one another.
-
B.
competitorCategory
Indicates that two entities operate in the same competitive category or market segment, positioning them as rivals within that domain.
-
C.
hasCompetitionCategory
Indicates that an entity is associated with a specific category or division within a competition.
-
D.
otherCategoriesInclude
chosen
Indicates that additional, non-primary categories associated with an entity are included or referenced.
-
E.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 12:45 a.m.