Triple
T37992116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logun Ede |
E947844
|
entity |
| Predicate | linkedDomain |
P112931
|
FINISHED |
| Object | forest |
—
|
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: forest | Statement: [Logun Ede, linkedDomain, forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDomain Context triple: [Logun Ede, linkedDomain, forest]
-
A.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
B.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
-
C.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
D.
sharesDomainWith
Indicates that two entities operate within, belong to, or are associated with the same domain or domain-like scope.
-
E.
involvedDomain
chosen
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
- 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_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:20 p.m.