Triple
T24731048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korandjé |
E618287
|
entity |
| Predicate | hasResearchBy |
P108399
|
FINISHED |
| Object | Lameen Souag |
—
|
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: Lameen Souag | Statement: [Korandjé, hasResearchBy, Lameen Souag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchBy Context triple: [Korandjé, hasResearchBy, Lameen Souag]
-
A.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
-
B.
hasResearched
chosen
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
C.
hasResearchComponent
Indicates that an entity includes, involves, or is associated with a research-related component or activity.
-
D.
hasResearchOutput
Indicates that an entity produces, is associated with, or is responsible for a particular research output or scholarly work.
-
E.
hasResearchValueIn
Indicates that something possesses significance, usefulness, or potential contribution within a specified research area, context, or domain.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 4:02 a.m.