Triple
T29860478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5668 Foucault |
E758298
|
entity |
| Predicate | hasNamesakeFor |
P99932
|
FINISHED |
| Object | Foucault pendulum |
—
|
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: Foucault pendulum | Statement: [5668 Foucault, hasNamesakeFor, Foucault pendulum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeFor Context triple: [5668 Foucault, hasNamesakeFor, Foucault pendulum]
-
A.
hasEarlierNamesake
Indicates that an entity shares its name with another entity that existed earlier in time.
-
B.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
C.
hasNamesakeFeature
chosen
Indicates that one entity has a feature (such as a place, object, or structure) that is named after another entity.
-
D.
hasNamesakeFamilyName
Indicates that two entities share the same family name, with one serving as the namesake for the other's family name.
-
E.
hasNamesakeRoleFor
Indicates that one entity holds a role or position that is named after, or serves as a namesake for, 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 29, 2026, 5:48 p.m.