Triple
T27605323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie and Joe |
E700163
|
entity |
| Predicate | publicationAudience |
P85592
|
FINISHED |
| Object | American servicemen |
—
|
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 servicemen | Statement: [Willie and Joe, publicationAudience, American servicemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationAudience Context triple: [Willie and Joe, publicationAudience, American servicemen]
-
A.
publicationScope
Indicates the extent, audience, or boundaries within which something (such as a work, data, or information) is made publicly available or distributed.
-
B.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
C.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
D.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
E.
book3Audience
chosen
Indicates that a particular book is intended for or targeted toward a specific audience.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 2:09 p.m.