Triple
T29120282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QT-1 |
E737159
|
entity |
| Predicate | storyExplores |
P1857
|
FINISHED |
| Object | conflict between logic and faith through QT-1 |
—
|
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: conflict between logic and faith through QT-1 | Statement: [QT-1, storyExplores, conflict between logic and faith through QT-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyExplores Context triple: [QT-1, storyExplores, conflict between logic and faith through QT-1]
-
A.
explores
chosen
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
B.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
explorationBy
Indicates a relationship where one entity conducts or performs exploration directed at or involving another entity.
-
D.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
E.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 11:25 a.m.