Triple
T29900079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaBeans |
E759384
|
entity |
| Predicate | componentDiscovery |
P7311
|
FINISHED |
| Object | introspection at design time |
—
|
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: introspection at design time | Statement: [JavaBeans, componentDiscovery, introspection at design time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentDiscovery Context triple: [JavaBeans, componentDiscovery, introspection at design time]
-
A.
schemeDiscovery
Indicates that an entity discovers, identifies, or uncovers a particular scheme, plan, or structured method.
-
B.
serviceDiscovery
Indicates a relationship where one component locates or identifies the network address or availability of another service dynamically, rather than using fixed configuration.
-
C.
discoveryMethod
chosen
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
D.
discoveryScope
Indicates the extent or range within which something can be found, detected, or identified.
-
E.
discoveryTarget
Indicates that one entity is the object, subject, or focus that another entity discovers or aims to discover.
- 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_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 6:06 p.m.