Triple
T37955448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 4 crew |
E946848
|
entity |
| Predicate | EVArole |
P161816
|
FINISHED |
| Object | ISS assembly and maintenance |
—
|
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: ISS assembly and maintenance | Statement: [Expedition 4 crew, EVArole, ISS assembly and maintenance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVArole Context triple: [Expedition 4 crew, EVArole, ISS assembly and maintenance]
-
A.
roleOfEvaChen
Indicates that a specified role, position, or function is held or performed by Eva Chen.
-
B.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
C.
EVAparticipant
chosen
Indicates participation of an entity in an extravehicular activity (EVA), such as being one of the actors involved in a spacewalk.
-
D.
eraRole
Indicates the specific role, function, or capacity an entity has within a particular historical or temporal era.
-
E.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.