Triple
T24387583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 121 Squadron RAF |
E614789
|
entity |
| Predicate | basedOnRecruitment |
P4674
|
FINISHED |
| Object | American volunteers |
—
|
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: American volunteers | Statement: [No. 121 Squadron RAF, basedOnRecruitment, American volunteers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnRecruitment Context triple: [No. 121 Squadron RAF, basedOnRecruitment, American volunteers]
-
A.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
B.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
C.
recruitmentBase
chosen
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
D.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
E.
enrollmentBasedOn
Indicates that one entity’s enrollment or registration status is determined or justified by another specified factor, condition, or entity.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29455e7fc8190841f909b970f6bd3 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.