Triple
T36062359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzungarian Gate |
E1043121
|
entity |
| Predicate | hasBeenUsedSince |
P2935
|
FINISHED |
| Object | ancient times |
—
|
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: ancient times | Statement: [Dzungarian Gate, hasBeenUsedSince, ancient times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenUsedSince Context triple: [Dzungarian Gate, hasBeenUsedSince, ancient times]
-
A.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
B.
usedSince
chosen
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
lastUsedFor
Indicates that one entity was the most recent purpose, function, or application for which another entity was used.
-
E.
lastUsedIn
Indicates that something was most recently utilized, applied, or referenced within a particular context, location, or instance.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.