Triple
T27103136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto Gets the Paper |
E686492
|
entity |
| Predicate | featuresNonHumanLead |
P193292
|
FINISHED |
| Object | animal protagonist |
—
|
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: animal protagonist | Statement: [Pluto Gets the Paper, featuresNonHumanLead, animal protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNonHumanLead Context triple: [Pluto Gets the Paper, featuresNonHumanLead, animal protagonist]
-
A.
leadType
Indicates the specific category or classification of a lead within a lead management or sales context.
-
B.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
-
C.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
D.
leadsFrom
Indicates that one entity serves as the starting point or origin from which another entity extends, proceeds, or is derived.
-
E.
leadConfigurationIncludes
Indicates that a given lead configuration contains or incorporates a specified component, option, or element as part of its setup.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 27, 2026, 8:49 a.m.