Triple
T33006957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seatruck Ferries |
E844528
|
entity |
| Predicate | hasCompetitiveFocus |
P15208
|
FINISHED |
| Object | freight capacity |
—
|
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: freight capacity | Statement: [Seatruck Ferries, hasCompetitiveFocus, freight capacity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitiveFocus Context triple: [Seatruck Ferries, hasCompetitiveFocus, freight capacity]
-
A.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
-
B.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
C.
hasCompetitionScope
chosen
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
-
D.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
E.
competitiveImportance
Indicates the degree to which something holds strategic or competitive significance relative to alternatives or rivals.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.