Triple
T317255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYC Ferry |
E7733
|
entity |
| Predicate | hasOperatorContractStart |
P11979
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [NYC Ferry, hasOperatorContractStart, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatorContractStart Context triple: [NYC Ferry, hasOperatorContractStart, 2017]
-
A.
operatesBetween
Indicates a relationship where an action, process, or influence functions or takes effect in the space, interval, or context separating two entities.
-
B.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
C.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
D.
canEnterIntoAgreementsWith
Indicates that one entity has the legal or formal capacity to make binding agreements or contracts with another entity.
-
E.
primaryOperator
Indicates that an entity serves as the main or leading operator responsible for performing or overseeing a specified operation or process in relation to another entity.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea65ca7081908093e6aaaf2d34f7 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.