Triple
T30250686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bylandt’s Brigade |
E769191
|
entity |
| Predicate | locationEngagement |
P164363
|
FINISHED |
| Object | Quatre Bras |
—
|
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: Quatre Bras | Statement: [Bylandt’s Brigade, locationEngagement, Quatre Bras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationEngagement Context triple: [Bylandt’s Brigade, locationEngagement, Quatre Bras]
-
A.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
B.
engagedLocation
chosen
Indicates that an entity is actively involved in or occupying a particular location during a specified activity or event.
-
C.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
D.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
-
E.
engagementNear
Indicates that one entity’s engagement or interaction occurs in close spatial or contextual proximity to 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: April 29, 2026, 7:40 p.m.