Triple
T18531681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR-11 |
E452843
|
entity |
| Predicate | hasMethodCount |
P132031
|
FINISHED |
| Object | 2 public methods in ContainerInterface |
—
|
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: 2 public methods in ContainerInterface | Statement: [PSR-11, hasMethodCount, 2 public methods in ContainerInterface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMethodCount Context triple: [PSR-11, hasMethodCount, 2 public methods in ContainerInterface]
-
A.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
-
B.
hasMonthCount
Indicates a relationship where an entity is associated with a specific number of months.
-
C.
hasWorkingMethod
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
D.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
E.
hasComponentCount
Indicates that an entity is associated with a specific number of components it contains or comprises.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fe35288190977c85ee0bb96264 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.