Triple
T30959015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humming-Fish |
E788756
|
entity |
| Predicate | forcedAction |
P4672
|
FINISHED |
| Object | leave their home |
—
|
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: leave their home | Statement: [Humming-Fish, forcedAction, leave their home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedAction Context triple: [Humming-Fish, forcedAction, leave their home]
-
A.
forcedActionDescribedIn
Indicates that an action was carried out under compulsion or coercion as described in a particular source or description.
-
B.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
C.
forcedBy
chosen
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
D.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
E.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:54 p.m.