Triple
T27733138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IEquatable`1 |
E697475
|
entity |
| Predicate | typeVisibility |
P100216
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [System.IEquatable`1, typeVisibility, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeVisibility Context triple: [System.IEquatable`1, typeVisibility, public]
-
A.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
-
B.
hasVisibilityCharacteristic
Indicates that one entity possesses a specific property or quality related to how visible or observable it is.
-
C.
typicalVisibility
Indicates the usual or expected degree to which one entity can be seen or perceived from another under normal conditions.
-
D.
visibilityRole
Indicates the role or level of access an entity has in determining what information or content is visible to others.
-
E.
accessModifier
chosen
Indicates the level or type of visibility/control applied to an entity, specifying how and from where it can be accessed or used.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369e16a08190853fdd8ac05800f6 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:12 p.m.