Triple
T30350784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | canBeRegisteredBy |
P121769
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [.info, canBeRegisteredBy, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRegisteredBy Context triple: [.info, canBeRegisteredBy, individuals]
-
A.
mayBeRegisteredAs
chosen
Indicates that an entity has the possibility or eligibility to be formally registered under a particular status, category, or registry.
-
B.
canBeUnregisteredWith
Indicates that one entity has the ability or option to be unregistered or removed from association with another entity.
-
C.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
D.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
E.
canBeEstablishedBy
Indicates that a particular state, condition, or relationship is able to be brought into existence or made valid through the actions or intervention of a specified entity.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 29, 2026, 7:56 p.m.