Triple
T33829622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqr |
E867059
|
entity |
| Predicate | relatedConstellationName |
P9993
|
FINISHED |
| Object | Aquarius |
E247364
|
NE 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: Aquarius | Statement: [Aqr, relatedConstellationName, Aquarius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedConstellationName Context triple: [Aqr, relatedConstellationName, Aquarius]
-
A.
relatedConstellation
chosen
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
B.
constellationName
Indicates that an entity is identified by the proper name of a constellation.
-
C.
parentConstellation
Indicates that one constellation is the larger or primary constellation within which another constellation is contained or of which it is a part.
-
D.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
E.
constellationFamily
Indicates that one constellation belongs to the same traditional family or grouping of constellations as another.
- F. None of above.
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a373602cf688190bc30131f7e8f9481 |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.