Triple
T25422996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatura |
E637033
|
entity |
| Predicate | campNumber |
P159441
|
FINISHED |
| Object | Dhurringile prisoner-of-war camp nearby |
—
|
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: Dhurringile prisoner-of-war camp nearby | Statement: [Tatura, campNumber, Dhurringile prisoner-of-war camp nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campNumber Context triple: [Tatura, campNumber, Dhurringile prisoner-of-war camp nearby]
-
A.
campPositionInNumbers
Indicates a relationship where a camp’s location or order is specified using numerical values (such as coordinates, rankings, or indexed positions).
-
B.
campLocation
Indicates the place or area where a camp is set up or located.
-
C.
numberOfCamps
Indicates the total count of camps associated with or involved in a given entity or situation.
-
D.
campSystem
Indicates a relationship where an entity is part of, managed by, or associated with a particular camp system or organized camp structure.
-
E.
campDesignation
Indicates that an entity is assigned or associated with a specific camp classification or label.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6be79b0819093a406e1f9b1348c |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 1:57 p.m.