Triple
T29900086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaBeans |
E759384
|
entity |
| Predicate | beanInfoClassPattern |
P8151
|
FINISHED |
| Object | XBeanInfo for bean X |
—
|
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: XBeanInfo for bean X | Statement: [JavaBeans, beanInfoClassPattern, XBeanInfo for bean X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beanInfoClassPattern Context triple: [JavaBeans, beanInfoClassPattern, XBeanInfo for bean X]
-
A.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
URLPattern
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
-
C.
configurationClass
Indicates that one entity serves as the configuration class (i.e., a class defining configuration settings or parameters) for another entity.
-
D.
patternTypeWithWhichPathInformation
Indicates a relationship where a pattern type is associated with or characterized by the presence of which-path (which-way) information in an experimental or observational context.
-
E.
patternTypeWithoutWhichPathInformation
Indicates that a pattern type is used or defined without including any information about the "which-path" (i.e., the specific route or path taken) in the underlying process or 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772e14d48190a9c4dda3d35d0f37 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:06 p.m.