Triple
T8243060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-World |
E192781
|
entity |
| Predicate | timeBehavior |
P73315
|
FINISHED |
| Object | time is unstable |
—
|
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: time is unstable | Statement: [Mid-World, timeBehavior, time is unstable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeBehavior Context triple: [Mid-World, timeBehavior, time is unstable]
-
A.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timeProperty
chosen
Indicates that one entity specifies, constrains, or characterizes a temporal aspect or timing-related attribute of another entity.
-
D.
timeDependence
Indicates that one entity’s state, value, or behavior is determined by or varies as a function of another entity over time.
-
E.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb786f65708190a92ec282b280c813 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.