Triple
T17871619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amvuttra |
E446848
|
entity |
| Predicate | isLongActing |
P129094
|
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: [Amvuttra, isLongActing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongActing Context triple: [Amvuttra, isLongActing, true]
-
A.
isLongRunning
Indicates that an action, process, or operation continues for an extended duration, typically longer than is usual or expected.
-
B.
isLongStanding
Indicates that a relationship, condition, or state has existed for a considerable or extended period of time.
-
C.
isLongOnlyEligible
Indicates that an entity is permitted to take only long (buy) positions and is not allowed to establish short (sell) positions.
-
D.
isShortLived
Indicates that an entity exists or remains in a particular state for only a brief or limited period of time.
-
E.
longLived
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa30ff8819090c51c1d7767e952 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:18 a.m.