Triple
T32440386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munger copper-plate inscription |
E828996
|
entity |
| Predicate | placeFound |
P80705
|
FINISHED |
| Object | Munger |
—
|
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: Munger | Statement: [Munger copper-plate inscription, placeFound, Munger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeFound Context triple: [Munger copper-plate inscription, placeFound, Munger]
-
A.
locationFound
chosen
Indicates that a particular entity is located or discovered at a specific place or position.
-
B.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
C.
loreLocation
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
D.
seeLocatedNear
Indicates that one entity visually perceives another entity that is situated nearby in physical space.
-
E.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 12:55 a.m.