Triple
T9218702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angoville-au-Plain |
E221304
|
entity |
| Predicate | churchUsedAs |
P86920
|
FINISHED |
| Object | field hospital during World War II |
—
|
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: field hospital during World War II | Statement: [Angoville-au-Plain, churchUsedAs, field hospital during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchUsedAs Context triple: [Angoville-au-Plain, churchUsedAs, field hospital during World War II]
-
A.
usedAsChurchFrom
Indicates that something functioned or was utilized as a church starting from a specified point in time.
-
B.
usedAsChurchUntil
Indicates that something served the function or role of a church up to a specified point in time.
-
C.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
D.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
E.
hasChapelUse
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda730f688190b64b2cc8c4898ac3 |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc687067fc81909da2d78fda0cdcfb |
completed | April 1, 2026, 12:36 a.m. |
Created at: March 30, 2026, 7:27 p.m.