Triple
T25643097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wally Funk |
E642883
|
entity |
| Predicate | relativePositionInCrew |
P125479
|
FINISHED |
| Object | spaceflight participant |
—
|
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: spaceflight participant | Statement: [Wally Funk, relativePositionInCrew, spaceflight participant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionInCrew Context triple: [Wally Funk, relativePositionInCrew, spaceflight participant]
-
A.
relativePositionWithinTeam
chosen
Indicates the positional or hierarchical relationship an entity holds relative to other members within the same team.
-
B.
relationshipToCrew
Indicates the specific familial, professional, or social connection an entity has to a given crew.
-
C.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
D.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 21, 2026, 5:46 p.m.