Triple
T32190109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Adamson (Born Free character) |
E822214
|
entity |
| Predicate | speciesWorkedWith |
P181777
|
FINISHED |
| Object | lion |
—
|
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: lion | Statement: [George Adamson (Born Free character), speciesWorkedWith, lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesWorkedWith Context triple: [George Adamson (Born Free character), speciesWorkedWith, lion]
-
A.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
B.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
C.
relatedWorkOfPerson
Indicates that a work (such as a publication, project, or creation) is associated with or produced by a particular person.
-
D.
collaboratedWithInKeyWork
Indicates that two or more entities worked together in creating or contributing to a specific, significant work or project.
-
E.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 12:35 a.m.