Triple
T5752389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | r/pics |
E126882
|
entity |
| Predicate | registrationNotRequiredFor |
P6844
|
FINISHED |
| Object | browsing |
—
|
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: browsing | Statement: [r/pics, registrationNotRequiredFor, browsing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationNotRequiredFor Context triple: [r/pics, registrationNotRequiredFor, browsing]
-
A.
registrationRequirement
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
-
B.
registrationRequiredToRead
Indicates that access to read the content is restricted and requires the user to complete a registration process beforehand.
-
C.
isNotRequiredFor
chosen
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
D.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
-
E.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.