Triple
T32368153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkut |
E827053
|
entity |
| Predicate | callSignOfCrewMemberNumber |
P78631
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Berkut, callSignOfCrewMemberNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignOfCrewMemberNumber Context triple: [Berkut, callSignOfCrewMemberNumber, 1]
-
A.
callSignForPerson
Indicates that a particular call sign is assigned to or used by a specific person.
-
B.
agencyOfCrewMember
Indicates that a particular organization or agency is responsible for employing, managing, or representing the specified crew member.
-
C.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
-
D.
callSignNumber
chosen
Indicates the specific identifying number assigned as a call sign to an entity for communication or identification purposes.
-
E.
mirOutgoingCrewMember
Indicates that a person is serving or has served as a departing crew member from the Mir space station.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9f57048190819d133d4caba58e |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:50 a.m.