Triple
T1712180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Technical Identifiers |
E37206
|
entity |
| Predicate | performsFunctionFor |
P13995
|
FINISHED |
| Object | global internet community |
—
|
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: global internet community | Statement: [Public Technical Identifiers, performsFunctionFor, global internet community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsFunctionFor Context triple: [Public Technical Identifiers, performsFunctionFor, global internet community]
-
A.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
B.
intendedFunction
chosen
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
E.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.