Triple
T31514807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stelmar Shipping |
E804037
|
entity |
| Predicate | acquiredInPeriod |
P172868
|
FINISHED |
| Object | mid-2000s |
—
|
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: mid-2000s | Statement: [Stelmar Shipping, acquiredInPeriod, mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredInPeriod Context triple: [Stelmar Shipping, acquiredInPeriod, mid-2000s]
-
A.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
B.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
C.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
-
D.
decoratedInPeriod
Indicates that an entity was decorated or ornamented during a specified historical or stylistic period.
-
E.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 9:52 p.m.