Triple
T19921602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DJI Avata |
E478807
|
entity |
| Predicate | supportsReturnToHome |
P137838
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [DJI Avata, supportsReturnToHome, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReturnToHome Context triple: [DJI Avata, supportsReturnToHome, true]
-
A.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
B.
supportsRoamingWith
Indicates that one entity enables or is compatible with another entity’s ability to operate or be accessed while roaming across different networks or locations.
-
C.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
D.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
E.
supportsResort
Indicates that one entity provides assistance, resources, or endorsement that helps maintain, operate, or promote a resort.
- F. None of above. chosen
Provenance (4 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c6919c8190a96106532580b6b6 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.