Triple
T33843204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wongar |
E867408
|
entity |
| Predicate | timeFramework |
P15775
|
FINISHED |
| Object | mythic time |
—
|
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: mythic time | Statement: [Wongar, timeFramework, mythic time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFramework Context triple: [Wongar, timeFramework, mythic time]
-
A.
timeScaleFramework
Indicates a relationship where one entity defines or provides the temporal measurement system or framework within which another entity’s timing, duration, or scheduling is interpreted.
-
B.
timeSystem
chosen
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
C.
timeDomain
Indicates that something is characterized, defined, or analyzed with respect to time rather than another domain (such as frequency or space).
-
D.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
E.
timeStructure
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.