Triple
T3578001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stellar Wind |
E75732
|
entity |
| Predicate | dataCollectedFrom |
P9384
|
FINISHED |
| Object | telecommunications companies |
—
|
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: telecommunications companies | Statement: [Stellar Wind, dataCollectedFrom, telecommunications companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectedFrom Context triple: [Stellar Wind, dataCollectedFrom, telecommunications companies]
-
A.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
B.
collectedThrough
chosen
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
C.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
D.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
E.
collectionOrigin
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0dd3e048190a0c6666e13ead9cd |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.