Triple
T27609710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-7 |
E700279
|
entity |
| Predicate | visitingAgency |
P163507
|
FINISHED |
| Object | CNES |
—
|
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: CNES | Statement: [Soyuz TM-7, visitingAgency, CNES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitingAgency Context triple: [Soyuz TM-7, visitingAgency, CNES]
-
A.
publicAgency
Indicates that an entity functions as a government-controlled or government-authorized organization that provides public services or carries out public administration.
-
B.
hostCountryAgency
Indicates that an agency belongs to, operates under the jurisdiction of, or officially represents the host country in a given context.
-
C.
publicAgencyFor
Indicates that one entity serves as a public agency acting on behalf of, or responsible for providing public services to, another entity.
-
D.
visitedByOrganization
Indicates that an organization has gone to or been physically present at a particular place or entity.
-
E.
relevantAgency
Indicates that an agency has authority, responsibility, or significant involvement in relation to a particular matter, entity, or action.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 2:10 p.m.