Triple
T24571746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethesda Circulator bus services |
E607979
|
entity |
| Predicate | targetAreaCharacteristic |
P3938
|
FINISHED |
| Object | urban center |
—
|
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: urban center | Statement: [Bethesda Circulator bus services, targetAreaCharacteristic, urban center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAreaCharacteristic Context triple: [Bethesda Circulator bus services, targetAreaCharacteristic, urban center]
-
A.
coreAreaCharacteristic
Indicates that a characteristic or feature is specifically associated with the core area of something, rather than its peripheral or secondary parts.
-
B.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
C.
serviceAreaCharacteristic
chosen
Indicates a relationship where a service area is associated with a specific attribute or feature that characterizes it.
-
D.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
domainCharacteristic
Indicates that a domain or area of interest possesses a particular characteristic or defining property.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9257ccc81908efcd9d047772492 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.