Triple
T33878499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brontë first editions |
E868420
|
entity |
| Predicate | typicalConditionFactor |
P72526
|
FINISHED |
| Object | presence of original endpapers |
—
|
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: presence of original endpapers | Statement: [Brontë first editions, typicalConditionFactor, presence of original endpapers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConditionFactor Context triple: [Brontë first editions, typicalConditionFactor, presence of original endpapers]
-
A.
typicalTrackCondition
Indicates the usual or standard state or quality of a track under normal conditions.
-
B.
typicalCircumstance
Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
-
C.
typicalAcceptanceCondition
Indicates the usual or standard conditions under which something is accepted or deemed acceptable.
-
D.
hasTypicalConditions
chosen
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:48 a.m.