Triple
T4838775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hezekiah |
E108127
|
entity |
| Predicate | publicWorks |
P30363
|
FINISHED |
| Object | fortification of Jerusalem’s walls |
—
|
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: fortification of Jerusalem’s walls | Statement: [Hezekiah, publicWorks, fortification of Jerusalem’s walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicWorks Context triple: [Hezekiah, publicWorks, fortification of Jerusalem’s walls]
-
A.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
B.
worksAgainst
Indicates that one entity actively opposes, counteracts, or undermines the goals, effects, or interests of another entity.
-
C.
workOn
chosen
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
D.
studioOfWork
Indicates that a particular studio is the place where a given work (such as a film, artwork, or recording) was created, produced, or primarily developed.
-
E.
worksAs
Indicates that an entity performs the role, job, or occupation specified by another entity.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.