Triple
T21002883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STAR |
E517339
|
entity |
| Predicate | trackingCoverage |
P64493
|
FINISHED |
| Object | large solid angle |
—
|
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: large solid angle | Statement: [STAR, trackingCoverage, large solid angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackingCoverage Context triple: [STAR, trackingCoverage, large solid angle]
-
A.
trajectoryCoverage
chosen
Indicates the extent to which a path or trajectory spans, visits, or accounts for the relevant space, time, or set of target points.
-
B.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
C.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
D.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
E.
coverageModel
Indicates a relationship where a specific model or framework defines, structures, or governs the extent and manner in which something is covered or addressed.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc38b8688190860fba1b58e1b3e6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.