Triple
T27495900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Currahee Regiment |
E694018
|
entity |
| Predicate | authorDepictingUnit |
P73801
|
FINISHED |
| Object | Stephen E. Ambrose |
—
|
NE NERFINISHED |
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: Stephen E. Ambrose | Statement: [Currahee Regiment, authorDepictingUnit, Stephen E. Ambrose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorDepictingUnit Context triple: [Currahee Regiment, authorDepictingUnit, Stephen E. Ambrose]
-
A.
authorOfDepiction
chosen
Indicates that one entity is the creator or author responsible for producing a particular depiction of another entity.
-
B.
composerOfDepictingWork
Indicates that an entity is the composer of a musical work that is itself a depiction or representation of another entity or subject.
-
C.
depictsAuthorOf
Indicates that one entity visually represents or portrays the person who is the author of another entity.
-
D.
authorDescribedIn
Indicates that information about an author is provided or discussed within a particular document or source.
-
E.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 1:08 p.m.