Triple
T8493470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abel (Abel of Sark) |
E201031
|
entity |
| Predicate | hasFictionalTrait |
P58963
|
FINISHED |
| Object | young |
—
|
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: young | Statement: [Abel (Abel of Sark), hasFictionalTrait, young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalTrait Context triple: [Abel (Abel of Sark), hasFictionalTrait, young]
-
A.
hasFictionalProperty
chosen
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
-
B.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
C.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
D.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
E.
hasFictionalPerformer
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe579b7088190b297b04527e36a2b |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.