Triple
T36486011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRITE-Austria |
E898933
|
entity |
| Predicate | targetObjects |
P198839
|
FINISHED |
| Object | bright stars |
—
|
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: bright stars | Statement: [BRITE-Austria, targetObjects, bright stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetObjects Context triple: [BRITE-Austria, targetObjects, bright stars]
-
A.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
B.
targetsVector
Indicates that one entity is directed toward, aimed at, or focused on another entity represented as a vector (e.g., a direction or target position).
-
C.
targetsProvidedBy
Indicates that one entity supplies or makes available specific targets for another entity to use or act upon.
-
D.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
E.
targetsProvision
Indicates that one entity is the intended recipient or beneficiary of a provision, service, or resource supplied by another entity.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 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. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 3, 2026, 4:10 p.m.