Triple
T36896663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebradillas |
E911907
|
entity |
| Predicate | usedToBeServedBy |
P19592
|
FINISHED |
| Object | railroad in Puerto Rico |
—
|
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: railroad in Puerto Rico | Statement: [Quebradillas, usedToBeServedBy, railroad in Puerto Rico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToBeServedBy Context triple: [Quebradillas, usedToBeServedBy, railroad in Puerto Rico]
-
A.
laterServedBy
Indicates that one entity is subsequently served or provided service by another entity at a later time.
-
B.
historicallyServedBy
chosen
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
C.
isServedOn
Indicates that one item (typically food or drink) is presented or provided atop or together with a particular surface, container, or accompaniment.
-
D.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
E.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd8e00c0819085b520069e25a5a3 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.