Triple
T10514173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Bäumer |
E247989
|
entity |
| Predicate | enlistsWith |
P29623
|
FINISHED |
| Object | his school classmates |
—
|
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: his school classmates | Statement: [Paul Bäumer, enlistsWith, his school classmates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enlistsWith Context triple: [Paul Bäumer, enlistsWith, his school classmates]
-
A.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
B.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
C.
joinedPluralityBy
chosen
Indicates that multiple entities collectively became members or participants of the same group, organization, or event through a shared act of joining.
-
D.
formedCoalitionWith
Indicates that two or more parties have joined together in a formal alliance or partnership to pursue shared goals or interests.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cade0c81908fcbd54a90106bf9 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.