Triple
T25976058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road |
E645942
|
entity |
| Predicate | mayServeFunction |
P159622
|
FINISHED |
| Object | collector road |
—
|
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: collector road | Statement: [State Road, mayServeFunction, collector road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayServeFunction Context triple: [State Road, mayServeFunction, collector road]
-
A.
mayServeFunction
chosen
Indicates that one entity is capable of performing, fulfilling, or acting in the role of a specified function for another entity or context.
-
B.
mayServe
Indicates that one entity is permitted or authorized to provide a service or function to another entity.
-
C.
mayServeOn
Indicates that one entity is permitted or eligible to serve on another entity, such as a group, body, or committee.
-
D.
mayProvideServiceIn
Indicates that one entity is permitted or authorized to offer or perform a service within the scope, area, or context defined by another entity.
-
E.
canServeOn
Indicates that one entity is eligible or permitted to serve on another entity, such as a group, body, or committee.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6050973a0819082e9b568175b7991 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:51 a.m.