Triple
T18799175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Army of Châlons |
E459718
|
entity |
| Predicate | statusAfterSedan |
P133063
|
FINISHED |
| Object | captured |
—
|
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: captured | Statement: [French Army of Châlons, statusAfterSedan, captured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterSedan Context triple: [French Army of Châlons, statusAfterSedan, captured]
-
A.
transportedAfter
Indicates that one entity is transported only after the transportation of another entity has occurred in time.
-
B.
statusAfterCunaxa
Indicates the status or condition of an entity following the events of the Battle of Cunaxa.
-
C.
stateCarried
Indicates that a particular state or condition is being actively maintained or borne by an entity or process.
-
D.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
E.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
- F. None of above. chosen
Provenance (4 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02273b481909bc250144a0ace32 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.