Triple
T3746679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telespazio |
E81225
|
entity |
| Predicate | isMajorPlayerIn |
P14730
|
FINISHED |
| Object | European space sector |
—
|
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 sector | Statement: [Telespazio, isMajorPlayerIn, European space sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorPlayerIn Context triple: [Telespazio, isMajorPlayerIn, European space sector]
-
A.
isMajor
chosen
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
B.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
C.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
D.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
E.
hasMajorFranchise
Indicates that an entity possesses or is associated with a primary, large-scale franchise within a broader domain or organization.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb69887c8190a3f1188ec85727b0 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.