Triple
T26657308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J band |
E666542
|
entity |
| Predicate | standardSystem |
P41769
|
FINISHED |
| Object | Johnson photometric system |
—
|
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: Johnson photometric system | Statement: [J band, standardSystem, Johnson photometric system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardSystem Context triple: [J band, standardSystem, Johnson photometric system]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
baseStandard
chosen
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
E.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:35 a.m.