Triple
T6903239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandectae |
E159543
|
entity |
| Predicate | containsApproximateNumberOfExtracts |
P74020
|
FINISHED |
| Object | 9000 |
—
|
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: 9000 | Statement: [Pandectae, containsApproximateNumberOfExtracts, 9000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsApproximateNumberOfExtracts Context triple: [Pandectae, containsApproximateNumberOfExtracts, 9000]
-
A.
hasApproximateBrickCount
Indicates that an entity is associated with an estimated or non-exact number of bricks.
-
B.
holdsApproximatelyFor
Indicates that a condition, relation, or value is valid only to an approximate degree or within a tolerance, rather than holding exactly.
-
C.
hasApproximateNumberOfMiniatures
Indicates that an entity is associated with an estimated or non-exact count of miniatures.
-
D.
haveApproximateCompleteCopies
Indicates that one entity possesses nearly full, but not necessarily perfectly exact, copies of another entity.
-
E.
hasApproximateNumberOfAttestedWords
Indicates that an entity is associated with an estimated or approximate count of words that are documented or attested for it.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d988a5b48190a9238047e86f314c |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.