Triple
T27075344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 51 |
E685447
|
entity |
| Predicate | crewMemberAgency |
P77314
|
FINISHED |
| Object | ESA |
—
|
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: ESA | Statement: [Expedition 51, crewMemberAgency, ESA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewMemberAgency Context triple: [Expedition 51, crewMemberAgency, ESA]
-
A.
agencyOfCrewMember
chosen
Indicates that a particular organization or agency is responsible for employing, managing, or representing the specified crew member.
-
B.
talentAgent
Indicates that one entity serves as a professional representative or manager (a talent agent) for another entity’s artistic, athletic, or entertainment career.
-
C.
componentAgency
Indicates that one entity functions as a constituent or subordinate agency within the organizational structure of another agency.
-
D.
productionCompanyAffiliation
Indicates a relationship where an entity is formally associated with or linked to a production company, typically through involvement in producing media or entertainment content.
-
E.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:30 a.m.