Triple
T32081630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BookMooch |
E819311
|
entity |
| Predicate | usesReputationSystem |
P180735
|
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, usesReputationSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReputationSystem Context triple: [BookMooch, usesReputationSystem, true]
-
A.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
reputationUsedFor
Indicates that an entity’s reputation is leveraged or applied for a particular purpose, function, or outcome.
-
C.
tributeAssessmentReputation
Indicates the evaluation of an entity’s reputation specifically in the context of determining or justifying a tribute assessment.
-
D.
associatedWithReputation
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
E.
hasViewReputation
Indicates that an entity holds a reputation or recognized standing specifically related to viewing, observing, or accessing something.
- F. None of above. chosen
Provenance (4 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: May 1, 2026, 12:24 a.m.