Triple
T9169567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Company Security Officer |
E220047
|
entity |
| Predicate | worksAtLevel |
P86605
|
FINISHED |
| Object | shore-based |
—
|
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: shore-based | Statement: [Company Security Officer, worksAtLevel, shore-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAtLevel Context triple: [Company Security Officer, worksAtLevel, shore-based]
-
A.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
B.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
laterWorksAt
Indicates that an entity begins working at a place or organization at a time later than another referenced time or employment situation.
-
E.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae0f3148190b111b22902cdb86c |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:22 p.m.