Triple
T22412954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol |
E554036
|
entity |
| Predicate | wasOneOfFirstKnown |
P128238
|
FINISHED |
| Object | eclipsing binaries |
—
|
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: eclipsing binaries | Statement: [Algol, wasOneOfFirstKnown, eclipsing binaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOneOfFirstKnown Context triple: [Algol, wasOneOfFirstKnown, eclipsing binaries]
-
A.
wasOneOfFirst
chosen
Indicates that the subject belonged to the earliest group or set of entities to perform, experience, or possess the specified role, status, or attribute.
-
B.
wasFirstOf
Indicates that the subject is the earliest or initial instance in a series, sequence, or group of similar entities or events.
-
C.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
D.
saidToBeTheFirst
Indicates that one entity is claimed or regarded as being the earliest or original instance of something relative to others.
-
E.
introducedAsFirst
Indicates that one entity is presented or mentioned before any others in a given context or sequence.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.