Triple
T24929878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zend Technologies |
E618954
|
entity |
| Predicate | roleInPHP |
P105433
|
FINISHED |
| Object | maintainer of Zend Engine |
—
|
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: maintainer of Zend Engine | Statement: [Zend Technologies, roleInPHP, maintainer of Zend Engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPHP Context triple: [Zend Technologies, roleInPHP, maintainer of Zend Engine]
-
A.
codeRole
chosen
Indicates a relationship where an entity serves a specific role or function within a piece of code or software system.
-
B.
roleInChickenfoot
Indicates that an entity participates in a game of Chickenfoot (a dominoes variant) in a specific role or capacity.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
roleInReasonML
Indicates that an entity holds a specific role or function within the ReasonML language, ecosystem, or community.
-
E.
roleInBlade
Indicates that an entity has a specific role or function within the context of a blade or bladed system.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 5:29 a.m.