Triple
T37552275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Quests |
E933614
|
entity |
| Predicate | rotationInterval |
P188596
|
FINISHED |
| Object | several hours |
—
|
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: several hours | Statement: [World Quests, rotationInterval, several hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationInterval Context triple: [World Quests, rotationInterval, several hours]
-
A.
rotationPeriod_hours
Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
-
B.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
C.
swingSpanRotationTime
Indicates the amount of time required for a swing span (such as a rotating bridge section) to complete its rotational movement from one position to another.
-
D.
usesInterval
Indicates that one entity operates, functions, or is defined within a specific time or value interval associated with another entity.
-
E.
timeCycle
chosen
Indicates a recurring temporal pattern or interval in which an event, state, or process regularly repeats.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.