Triple
T291069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Broca |
E5993
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Pierre |
E3672
|
NE 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: Pierre | Statement: [Paul Broca, givenName, Pierre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pierre Context triple: [Paul Broca, givenName, Pierre]
-
A.
Pierre
chosen
Pierre is a masculine given name of French origin that has been borne by numerous notable figures in history, arts, and science.
-
B.
René
René is a French given name commonly used for males and historically associated with several notable figures in politics, arts, and philosophy.
-
C.
Jacques
Jacques is the French form of the given name James, commonly used in French-speaking countries.
-
D.
Eugène
Eugène is a masculine given name of French origin, derived from the Greek "Eugenios," meaning "well-born" or "noble."
-
E.
Georges
Georges is a masculine given name of Greek origin, commonly used in French-speaking countries and derived from the name George, meaning "farmer" or "earthworker."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4f78bc81909a64fd6aaec3b504 |
completed | Feb. 28, 2026, 3:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3d4de751081908703ac3d1dba9f7b |
completed | March 1, 2026, 5:55 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.