Triple
T36347444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollow Earth Aerial Vehicle |
E895103
|
entity |
| Predicate | technologyUser |
P76504
|
FINISHED |
| Object | Monarch scientists |
—
|
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: Monarch scientists | Statement: [Hollow Earth Aerial Vehicle, technologyUser, Monarch scientists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyUser Context triple: [Hollow Earth Aerial Vehicle, technologyUser, Monarch scientists]
-
A.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
B.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
-
C.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
D.
technologyUsedBy
chosen
Indicates that a particular technology is employed or utilized by a specified entity.
-
E.
technologyEnabled
Indicates that one entity provides or supports the technological means that allow another entity, process, or capability to function or be carried out.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.