Triple
T19118883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 24970 |
E467982
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | Per OB2 |
—
|
NE NERFINISHED |
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: Per OB2 | Statement: [HD 24970, memberOf, Per OB2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Per OB2 Context triple: [HD 24970, memberOf, Per OB2]
-
A.
Per OB2
chosen
Per OB2 is an OB stellar association in the constellation Perseus, containing numerous young, massive, hot stars formed from the same giant molecular cloud.
-
B.
Mon OB2
Mon OB2 is a young stellar association in the constellation Monoceros, rich in massive, hot OB-type stars that illuminate surrounding nebulae.
-
C.
Per OB2 association
The Per OB2 association is a nearby group of young, massive OB-type stars in the constellation Perseus, formed from the same molecular cloud and moving together through space.
-
D.
OBN
OBN is the three-letter IATA airport code assigned to Oban Airport in Scotland.
-
E.
OBN
OBN is the National Rail station code for Oban railway station in Argyll and Bute, Scotland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3c756a88190942930e6ae7242a7 |
completed | April 20, 2026, 8:28 a.m. |
Created at: April 10, 2026, 12:05 p.m.