Triple
T156751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleiades |
E3196
|
entity |
| Predicate | interstellarMediumOrigin |
P3654
|
FINISHED |
| Object | unrelated passing dust cloud |
—
|
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: unrelated passing dust cloud | Statement: [Pleiades, interstellarMediumOrigin, unrelated passing dust cloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interstellarMediumOrigin Context triple: [Pleiades, interstellarMediumOrigin, unrelated passing dust cloud]
-
A.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
B.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
-
D.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
E.
cityOfOriginal
Indicates the city from which something or someone originally comes or was first created or established.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.