Triple
T36756005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxima |
E908052
|
entity |
| Predicate | featuresRealFacilities |
P12416
|
FINISHED |
| Object | European Space Agency facilities |
—
|
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: European Space Agency facilities | Statement: [Proxima, featuresRealFacilities, European Space Agency facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRealFacilities Context triple: [Proxima, featuresRealFacilities, European Space Agency facilities]
-
A.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
B.
publicFacilities
Indicates that the subject provides, contains, or is associated with facilities intended for use by the general public.
-
C.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
D.
campusFacility
Indicates that one entity is a facility that is located on or belongs to a particular campus.
-
E.
findingOnFacilities
Indicates a relationship where an inspection or assessment identifies a specific issue, observation, or result associated with particular facilities.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.