Triple
T4135793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel Soft |
E85150
|
entity |
| Predicate | isSingleUse |
P10110
|
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: [Angel Soft, isSingleUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSingleUse Context triple: [Angel Soft, isSingleUse, true]
-
A.
isDayUseOnly
Indicates that the entity may only be used or accessed during daytime hours and not overnight.
-
B.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
C.
canBeReceivedOnce
chosen
Indicates that the referenced item, benefit, or action may only be obtained a single time by a given recipient.
-
D.
isOneWay
Indicates that the relationship or action proceeds in only one direction from a source entity to a target entity, without a corresponding reverse relation.
-
E.
hasSinglePlayer
Indicates that something includes, supports, or is designed for a single-player mode or experience.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.