Triple
T18695661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crab Nebula |
E457107
|
entity |
| Predicate | usedAsStandard |
P132328
|
FINISHED |
| Object | X-ray astronomy flux calibrator |
—
|
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: X-ray astronomy flux calibrator | Statement: [Crab Nebula, usedAsStandard, X-ray astronomy flux calibrator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsStandard Context triple: [Crab Nebula, usedAsStandard, X-ray astronomy flux calibrator]
-
A.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
B.
implementedAsStandardBy
Indicates that a standard is put into practice or realized through implementation by a specific entity (such as an organization, system, or component).
-
C.
usedAsGeneral
Indicates that an entity served in the role or capacity of a general, typically as a high-ranking military commander.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
becameStandardFor
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
- F. None of above. chosen
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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.