Triple
T3383642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pararaton |
E71244
|
entity |
| Predicate | historicalReliability |
P675
|
FINISHED |
| Object | partly legendary |
—
|
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: partly legendary | Statement: [Pararaton, historicalReliability, partly legendary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalReliability Context triple: [Pararaton, historicalReliability, partly legendary]
-
A.
historicalExistence
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
-
B.
historicalEvidence
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
C.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
D.
historicalAssessment
chosen
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ec85d08190b28110157c39435f |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.