Triple
T9027845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scribble for iPadOS |
E216091
|
entity |
| Predicate | allowsInputIn |
P46417
|
FINISHED |
| Object | any text field |
—
|
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: any text field | Statement: [Scribble for iPadOS, allowsInputIn, any text field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsInputIn Context triple: [Scribble for iPadOS, allowsInputIn, any text field]
-
A.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
allowsText
chosen
Indicates that one entity permits or supports the use, input, or display of textual content in relation to another entity.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
E.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.