Triple
T37205966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HO Librae |
E922169
|
entity |
| Predicate | hasTransitDetections |
P201712
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [HO Librae, hasTransitDetections, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransitDetections Context triple: [HO Librae, hasTransitDetections, false]
-
A.
hasTransitTrafficLevel
Indicates the level or intensity of transit traffic associated with an entity, such as a road segment, route, or area.
-
B.
hasTransitFocus
Indicates that something is oriented toward, prioritizes, or is primarily concerned with transit or transportation services.
-
C.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
D.
hasTrafficMonitoring
Indicates that an entity is equipped with or associated with a system or capability for observing, measuring, or analyzing traffic conditions or flows.
-
E.
hasTrafficFeature
Indicates that an entity possesses or is associated with a specific traffic-related characteristic, element, or infrastructure feature.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
| PDg | Predicate description generation | batch_6a0017dc2cd48190a89c3e9c71708519 |
completed | May 10, 2026, 5:30 a.m. |
Created at: May 3, 2026, 4:15 p.m.