Triple
T1906290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The American Claimant |
E38011
|
entity |
| Predicate | hasFictionalForm |
P33843
|
FINISHED |
| Object | prose |
—
|
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: prose | Statement: [The American Claimant, hasFictionalForm, prose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalForm Context triple: [The American Claimant, hasFictionalForm, prose]
-
A.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
B.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
C.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
D.
hasNotableFictionalBearer
Indicates that an entity is associated with at least one well-known fictional character that bears its name or designation.
-
E.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb34c4a64819096e12b152b84c334 |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:35 p.m.