Triple
T5752387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | r/pics |
E126882
|
entity |
| Predicate | registrationRequiredFor |
P28439
|
FINISHED |
| Object | posting |
—
|
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: posting | Statement: [r/pics, registrationRequiredFor, posting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationRequiredFor Context triple: [r/pics, registrationRequiredFor, posting]
-
A.
registrationRequiredToRead
Indicates that access to read the content is restricted and requires the user to complete a registration process beforehand.
-
B.
registrationRequirement
chosen
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
-
C.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
D.
campaignRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for a campaign associated with another entity.
-
E.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
- 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.