Triple
T2157733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutenberg Bible copies |
E47929
|
entity |
| Predicate | haveApproximateCompleteCopies |
P36316
|
FINISHED |
| Object | about 21 complete copies |
—
|
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: about 21 complete copies | Statement: [Gutenberg Bible copies, haveApproximateCompleteCopies, about 21 complete copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveApproximateCompleteCopies Context triple: [Gutenberg Bible copies, haveApproximateCompleteCopies, about 21 complete copies]
-
A.
hasCopy
Indicates that one entity possesses, contains, or maintains a duplicate or instance of another entity.
-
B.
hasReplicaDisplays
Indicates that an entity features or presents one or more replica items as displays.
-
C.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
-
D.
hasQuorum
Indicates that the number of required participants or members is sufficient to validly conduct the specified activity or decision.
-
E.
hasNumberOfCasesApprox
Indicates that an entity is associated with an approximate (not exact) count of cases.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe68fe0c8190beb5db003738a6e5 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:44 p.m.