Triple
T36547011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardings |
E901164
|
entity |
| Predicate | rebuildsCity |
P39665
|
FINISHED |
| Object | Dale |
—
|
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: Dale | Statement: [Bardings, rebuildsCity, Dale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildsCity Context triple: [Bardings, rebuildsCity, Dale]
-
A.
cityRebuiltBy
Indicates that a city has been reconstructed or significantly restored through the actions, efforts, or initiative of a specified agent or entity.
-
B.
cityRebuiltAfter
Indicates that a city was reconstructed or significantly restored following a prior event of destruction or severe damage.
-
C.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
D.
rebuildPlace
chosen
Indicates that an entity restores or reconstructs a place that was previously damaged, destroyed, or altered.
-
E.
buildCity
Indicates the action of constructing or establishing a city at a particular location or within a certain context.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.