Triple
T20613021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collinder 121 |
E506493
|
entity |
| Predicate | usedForStudy |
P70296
|
FINISHED |
| Object | local star formation |
—
|
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: local star formation | Statement: [Collinder 121, usedForStudy, local star formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForStudy Context triple: [Collinder 121, usedForStudy, local star formation]
-
A.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
B.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
studiesFor
Indicates that one entity engages in studying or academic preparation with the purpose of achieving or supporting another entity (such as a goal, exam, or qualification).
-
E.
isSubjectOfStudy
chosen
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.