Triple
T36919532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tweedy's farm |
E913140
|
entity |
| Predicate | escapeMethodUsed |
P186689
|
FINISHED |
| Object | homemade airplane |
—
|
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: homemade airplane | Statement: [Tweedy's farm, escapeMethodUsed, homemade airplane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeMethodUsed Context triple: [Tweedy's farm, escapeMethodUsed, homemade airplane]
-
A.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
B.
escapeFunction
Indicates that one entity serves to safely convert or encode another entity so that it can be used without causing unintended effects or security issues.
-
C.
escapedTo
Indicates that an entity fled or broke free from a place, situation, or captor and reached another location as a result.
-
D.
escapeOf
Indicates that one entity escapes, is released, or leaks out from another entity or containing context.
-
E.
escapedBy
Indicates that an entity is freed or enabled to escape through the actions or intervention of another entity.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.