Triple

T35692069
Position Surface form Disambiguated ID Type / Status
Subject IV Corps (British Army) E1031319 entity
Predicate alsoKnownAs P39 FINISHED
Object Fourth Army Corps
Fourth Army Corps, also known as IV Corps, was a major British Army field formation that saw significant service in both World War I and World War II.
E2152056 NE 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: Fourth Army Corps | Statement: [IV Corps (British Army), alsoKnownAs, Fourth Army Corps]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Fourth Army Corps
Triple: [IV Corps (British Army), alsoKnownAs, Fourth Army Corps]
Generated description
Fourth Army Corps, also known as IV Corps, was a major British Army field formation that saw significant service in both World War I and World War II.

Provenance (5 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_69f76e0c73ec819080ab60a9e2f5f1f6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a07e0c9081909926c9359ab10ab4 completed May 3, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a387292c00c8190be286ecd9b07f97c completed June 21, 2026, 11:24 p.m.
NEDg Description generation batch_6a387468b0888190a0e17ff71a7026b3 completed June 21, 2026, 11:31 p.m.
NED2 Entity disambiguation (via description) batch_6a3874d125608190a5b65e83823684d8 completed June 21, 2026, 11:33 p.m.
Created at: May 3, 2026, 4:05 p.m.