Triple
T9004152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | App protocol (SwiftUI) |
E215101
|
entity |
| Predicate | bodyReturnType |
P85669
|
FINISHED |
| Object | Scene |
—
|
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: Scene | Statement: [App protocol (SwiftUI), bodyReturnType, Scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyReturnType Context triple: [App protocol (SwiftUI), bodyReturnType, Scene]
-
A.
typeOfBody
Indicates that one entity is the classification or kind of physical body that the other entity is.
-
B.
publicBodyType
Indicates the classification or category of a public body (such as its organizational or legal type) within a governmental or public-sector context.
-
C.
bodyRetrievedBy
Indicates that a deceased body is collected, recovered, or taken into custody by a specified agent or organization.
-
D.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
E.
bodyPattern
Indicates a recurring or characteristic configuration, arrangement, or sequence exhibited by a body or physical form.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6959497c8190a748c78504dd2eb6 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.