Triple
T22591871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkut |
E564968
|
entity |
| Predicate | laterAccessModel |
P18355
|
FINISHED |
| Object | open registration |
—
|
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: open registration | Statement: [Orkut, laterAccessModel, open registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAccessModel Context triple: [Orkut, laterAccessModel, open registration]
-
A.
laterAccessedBy
Indicates that an entity is subsequently accessed or used by another entity at a later point in time.
-
B.
hasAccessModel
chosen
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
C.
laterMode
Indicates that one event, state, or mode occurs after another in time.
-
D.
accessModelIntroduced
Indicates that a particular method, mechanism, or pathway for accessing something has been newly introduced or made available.
-
E.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16162c2cc8190a506776ac52356d7 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.