Triple
T29860344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foucault pendulum |
E758294
|
entity |
| Predicate | firstPublicDemonstrationLocation |
P16920
|
FINISHED |
| Object | Panthéon, Paris |
—
|
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: Panthéon, Paris | Statement: [Foucault pendulum, firstPublicDemonstrationLocation, Panthéon, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicDemonstrationLocation Context triple: [Foucault pendulum, firstPublicDemonstrationLocation, Panthéon, Paris]
-
A.
firstUSPerformanceLocation
Indicates the location where an entity was first performed in the United States.
-
B.
placeOfFirstSignificantReception
Indicates the location where something (such as a work, idea, or person) was first received with notable attention, recognition, or impact.
-
C.
firstUnveiledInCity
chosen
Indicates that something was publicly revealed, introduced, or debuted for the first time in a particular city.
-
D.
firstPerformanceLocationOfWorkAppearingIn
Indicates the location where a work was first performed or premiered.
-
E.
firstSuccessfulXerographicExperimentPlace
Indicates the location where an entity carried out its first successful xerographic experiment.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0149447e448190b0480943de0691ee |
completed | May 11, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_6a0148e2c39c8190a3ad6ea6be902c04 |
completed | May 11, 2026, 3:11 a.m. |
Created at: April 29, 2026, 5:48 p.m.