Triple
T27524765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panina |
E694802
|
entity |
| Predicate | relevanceIn |
P162677
|
FINISHED |
| Object | human evolution studies |
—
|
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: human evolution studies | Statement: [Panina, relevanceIn, human evolution studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relevanceIn Context triple: [Panina, relevanceIn, human evolution studies]
-
A.
relevanceDate
Indicates the date or time at which something becomes relevant, applicable, or significant in the given context.
-
B.
relevantToInstitution
Indicates that something has a meaningful connection, applicability, or significance to a particular institution.
-
C.
hasCanonicalRelevance
Indicates that something is considered standard, authoritative, or centrally important within an established canon or reference framework.
-
D.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
E.
relevantAuthority
Indicates that an entity has official power, jurisdiction, or responsibility over another entity or matter within a given context.
- F. None of above. chosen
Provenance (4 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f2e2df88190948551f6fd67a65a |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:23 p.m.