Triple
T28195044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEL-1 |
E716419
|
entity |
| Predicate | sisterBeamline |
P164120
|
FINISHED |
| Object | FEL-2 |
—
|
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: FEL-2 | Statement: [FEL-1, sisterBeamline, FEL-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterBeamline Context triple: [FEL-1, sisterBeamline, FEL-2]
-
A.
sisterObservatory
Indicates that two observatories are formally paired or linked as sister institutions, typically for collaboration or shared missions.
-
B.
sisterLine
Indicates that one entity is a sister of another within a family or genealogical relationship.
-
C.
sisterBase
Indicates that one entity is the sister of another, sharing at least one parent and being female relative to the other entity.
-
D.
sisterStation
Indicates that two broadcast stations are related as counterparts, typically serving different areas or platforms under common ownership or affiliation.
-
E.
hasSisterTelescope
Indicates that one telescope is considered a sister telescope to another, typically due to a close partnership, shared design, or coordinated observational role.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d058188190b71796a530a202f6 |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:27 p.m.