Triple
T30292536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Square |
E770417
|
entity |
| Predicate | wasLaidOutDuringReignOf |
P7942
|
FINISHED |
| Object | Charles IV |
—
|
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: Charles IV | Statement: [Charles Square, wasLaidOutDuringReignOf, Charles IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLaidOutDuringReignOf Context triple: [Charles Square, wasLaidOutDuringReignOf, Charles IV]
-
A.
builtDuringReignOf
chosen
Indicates that something was constructed while a particular ruler or authority was in power.
-
B.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
-
C.
wroteDuringReignOf
Indicates that the writing of a work by one entity took place while another entity was reigning or in power.
-
D.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
E.
capturedDuringReignOf
Indicates that one entity was captured while another entity was in power or ruling (i.e., during the time span of that entity’s reign).
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813474208190b3e2f0ad7d2b9aab |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:47 p.m.