Triple
T28507563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pamac |
E721398
|
entity |
| Predicate | implementsFrontendFor |
P130301
|
FINISHED |
| Object | pacman |
—
|
NE NERFINISHED |
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: pacman | Statement: [pamac, implementsFrontendFor, pacman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementsFrontendFor Context triple: [pamac, implementsFrontendFor, pacman]
-
A.
hasFrontend
Indicates that one entity serves as the user-facing interface or presentation layer for another entity.
-
B.
frontEndFor
chosen
Indicates that one entity serves as the user-facing interface or access point through which another underlying system, service, or component is used or interacted with.
-
C.
implementedFor
Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements of, another entity.
-
D.
frontEnd
Indicates that one entity serves as the user-facing or client-side component in relation to another system or application.
-
E.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:10 a.m.