Triple
T37992107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logun Ede |
E947844
|
entity |
| Predicate | inheritsAspectFrom |
P165096
|
FINISHED |
| Object | Oxóssi |
—
|
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: Oxóssi | Statement: [Logun Ede, inheritsAspectFrom, Oxóssi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritsAspectFrom Context triple: [Logun Ede, inheritsAspectFrom, Oxóssi]
-
A.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
B.
inheritsMembersFrom
chosen
Indicates that one entity receives or derives its members, properties, or characteristics from another entity.
-
C.
inheritsThrough
Indicates that one entity acquires rights, traits, or properties from another entity via an intermediate source or lineage rather than directly.
-
D.
inheritsSymbolFrom
Indicates that one entity derives or receives its symbolic representation or notation from another entity.
-
E.
inheritsMessagePropertyFrom
Indicates that one message derives or receives a specific property or attribute from another message.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.