Triple
T32081640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BookMooch |
E819311
|
entity |
| Predicate | hasRegistrationRequired |
P124298
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BookMooch, hasRegistrationRequired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistrationRequired Context triple: [BookMooch, hasRegistrationRequired, true]
-
A.
requiresRegistrationFor
chosen
Indicates that one entity can only access, use, or participate in another entity if a prior registration process has been completed.
-
B.
hasReferralRequirement
Indicates that one entity requires a formal referral from another entity before access, participation, or service can occur.
-
C.
registrationRequirement
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
-
D.
mustRegisterWith
Indicates that one entity is required or obligated to formally enroll or record its information with another entity or authority.
-
E.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
Created at: May 1, 2026, 12:24 a.m.