Triple
T27671647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belval Campus |
E697678
|
entity |
| Predicate | isFlagshipSiteOf |
P43978
|
FINISHED |
| Object | University of Luxembourg |
—
|
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: University of Luxembourg | Statement: [Belval Campus, isFlagshipSiteOf, University of Luxembourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFlagshipSiteOf Context triple: [Belval Campus, isFlagshipSiteOf, University of Luxembourg]
-
A.
isFlagshipServiceOf
Indicates that a particular service is the primary, leading, or most prominent offering of a given organization or provider.
-
B.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
C.
hasFlagshipIn
chosen
Indicates that an entity designates a particular location or branch as its primary or flagship presence.
-
D.
isSatelliteSiteOf
Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
-
E.
originalFlagshipName
Indicates the original name by which a flagship entity (such as a primary product, vessel, or brand) was first designated or known.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:41 p.m.