Triple
T35790728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tic Tac (UFO) |
E1034684
|
entity |
| Predicate | maneuverabilityDescribedAs |
P183672
|
FINISHED |
| Object | highly maneuverable |
—
|
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: highly maneuverable | Statement: [Tic Tac (UFO), maneuverabilityDescribedAs, highly maneuverable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maneuverabilityDescribedAs Context triple: [Tic Tac (UFO), maneuverabilityDescribedAs, highly maneuverable]
-
A.
maneuverType
Indicates the specific kind or category of maneuver being performed or described in a given context.
-
B.
hasAmphibiousCapability
Indicates that an entity possesses the ability to operate effectively in both water and land environments.
-
C.
notableManeuver
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
-
D.
amphibiousCapacity
Indicates the ability of an entity to operate effectively in both water and on land.
-
E.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22e0ff88190989a5df84fca968b |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a162672481909773f8383d91159a |
completed | May 3, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:06 p.m.