Triple
T24056802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus boisei |
E595828
|
entity |
| Predicate | associatedResearcher |
P28320
|
FINISHED |
| Object | Louis Leakey |
—
|
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: Louis Leakey | Statement: [Paranthropus boisei, associatedResearcher, Louis Leakey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedResearcher Context triple: [Paranthropus boisei, associatedResearcher, Louis Leakey]
-
A.
associatedScholar
Indicates a relationship where a scholar is linked or connected to another entity (such as a work, institution, or concept) through relevant academic or intellectual involvement.
-
B.
researchCoDirectedBy
Indicates that a research project or activity is jointly directed or supervised by two or more entities.
-
C.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
-
D.
hasResearcher
chosen
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
-
E.
researchOperator
Indicates that an entity conducts, manages, or is responsible for carrying out research activities on or 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:34 p.m.