Triple
T36531250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kearny Connection |
E900448
|
entity |
| Predicate | reducedNeedForTransferAt |
P102026
|
FINISHED |
| Object | Hoboken Terminal |
—
|
NE NERFINISHED |
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: Hoboken Terminal | Statement: [Kearny Connection, reducedNeedForTransferAt, Hoboken Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedNeedForTransferAt Context triple: [Kearny Connection, reducedNeedForTransferAt, Hoboken Terminal]
-
A.
isReducedDuringUseTo
Indicates that the quantity, intensity, or effectiveness of one entity decreases as a direct result of being used or consumed.
-
B.
reducedNumberOf
chosen
Indicates that the subject has a smaller quantity or count of the specified object or attribute compared to a prior state or reference level.
-
C.
reduces
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
D.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
E.
reducedCapacity
Indicates that an entity is functioning with less than its normal or full capacity, ability, or effectiveness.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.