Triple
T22784624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Éditions Gallimard |
E563930
|
entity |
| Predicate | hasBacklistSize |
P143251
|
FINISHED |
| Object | large and historically important catalog |
—
|
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: large and historically important catalog | Statement: [Éditions Gallimard, hasBacklistSize, large and historically important catalog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBacklistSize Context triple: [Éditions Gallimard, hasBacklistSize, large and historically important catalog]
-
A.
hasBackTo
Indicates that one entity is positioned or oriented with its back facing toward another entity.
-
B.
hasCatalogueSize
chosen
Indicates that an entity possesses a catalogue containing a specified number of items or entries.
-
C.
hasWaitingList
Indicates that there exists a queue or list of entities waiting for access to, or participation in, the referenced resource, service, or opportunity.
-
D.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
E.
hasBackIssues
Indicates that an entity experiences or possesses problems, conditions, or complications related to its back.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c30b4dc8190a5e23f4ce7feb300 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.