Triple
T16920947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fucino |
E410441
|
entity |
| Predicate | roleInSpaceSector |
P78410
|
FINISHED |
| Object | key European space technology hub |
—
|
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: key European space technology hub | Statement: [Fucino, roleInSpaceSector, key European space technology hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSpaceSector Context triple: [Fucino, roleInSpaceSector, key European space technology hub]
-
A.
spaceSectorRole
chosen
Indicates the functional role or responsibility an entity holds within a specific space sector or domain.
-
B.
roleInSpaceX
Indicates that one entity holds or has held a specific role, position, or function within the organization SpaceX.
-
C.
roleInRelationToNASA
Indicates that one entity holds a specific role, position, or functional relationship with respect to NASA.
-
D.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
E.
roleInISRO
Indicates that an entity holds or has held a specific role, position, or responsibility within the Indian Space Research Organisation (ISRO).
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdee252c81908621b2ca897416e9 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.