Triple
T20327567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO/Uppsala Survey of the ESO(B) Atlas |
E492380
|
entity |
| Predicate | bandDesignation |
P139721
|
FINISHED |
| Object | B band |
—
|
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: B band | Statement: [ESO/Uppsala Survey of the ESO(B) Atlas, bandDesignation, B band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandDesignation Context triple: [ESO/Uppsala Survey of the ESO(B) Atlas, bandDesignation, B band]
-
A.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
B.
clusterDesignation
Indicates that an entity is assigned to or identified as part of a specific cluster or grouping.
-
C.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
-
D.
beltDesignOwner
Indicates that a particular entity is the owner or rights holder of a specific belt design.
-
E.
wellDesignation
Indicates that an entity is assigned a specific well identifier or label, typically denoting its position or role within a well-based system (such as a plate or grid of wells).
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:21 a.m.