Triple
T7970004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Droid Depot |
E185298
|
entity |
| Predicate | buildExperienceDuration |
P17474
|
FINISHED |
| Object | approximately 20 minutes |
—
|
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: approximately 20 minutes | Statement: [Droid Depot, buildExperienceDuration, approximately 20 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildExperienceDuration Context triple: [Droid Depot, buildExperienceDuration, approximately 20 minutes]
-
A.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
-
B.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
C.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
D.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
E.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd304dc8190b9feee5e17fc66db |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.