Triple
T36785937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermians |
E908910
|
entity |
| Predicate | recruitFor |
P28396
|
FINISHED |
| Object | real space mission |
—
|
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: real space mission | Statement: [Thermians, recruitFor, real space mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitFor Context triple: [Thermians, recruitFor, real space mission]
-
A.
recruitsFor
chosen
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
B.
recruit
Indicates bringing a person or group into an organization, cause, or activity, typically to join or participate.
-
C.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
D.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
E.
recruitingFocus
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.