Triple
T16075551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV9 |
E389970
|
entity |
| Predicate | laterUsages |
P5014
|
FINISHED |
| Object | visited and reused in later periods |
—
|
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: visited and reused in later periods | Statement: [KV9, laterUsages, visited and reused in later periods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUsages Context triple: [KV9, laterUsages, visited and reused in later periods]
-
A.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
B.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
E.
subsequentUse
chosen
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.