Triple
T32386798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSLC |
E827562
|
entity |
| Predicate | hasTrackingNetwork |
P180839
|
FINISHED |
| Object | ground-based tracking stations |
—
|
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: ground-based tracking stations | Statement: [JSLC, hasTrackingNetwork, ground-based tracking stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackingNetwork Context triple: [JSLC, hasTrackingNetwork, ground-based tracking stations]
-
A.
hasTrailNetwork
Indicates that an entity possesses or is associated with a system of interconnected trails or paths.
-
B.
isTracked
Indicates that an entity’s state, behavior, or presence is being monitored or recorded over time.
-
C.
isTrackedBy
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
D.
supportsTrackingSystem
chosen
Indicates that an entity provides compatibility with, or functionality for, a tracking system, enabling items or activities to be monitored or recorded.
-
E.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 1, 2026, 12:51 a.m.