Triple
T692795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principia Mathematica |
E13830
|
entity |
| Predicate | hasFamousResult |
P1706
|
FINISHED |
| Object | derivation of 1+1=2 |
—
|
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: derivation of 1+1=2 | Statement: [Principia Mathematica, hasFamousResult, derivation of 1+1=2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousResult Context triple: [Principia Mathematica, hasFamousResult, derivation of 1+1=2]
-
A.
notableOutcome
chosen
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
B.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
-
C.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
D.
hasWonCompetition
Indicates that an entity has achieved victory in a competition or contest against others.
-
E.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0b05f2c8190876c73db15b489a2 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.