Triple
T27706556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pass Laws in South Africa |
E698572
|
entity |
| Predicate | requiredDocument |
P63443
|
FINISHED |
| Object | pass book |
—
|
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: pass book | Statement: [Pass Laws in South Africa, requiredDocument, pass book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredDocument Context triple: [Pass Laws in South Africa, requiredDocument, pass book]
-
A.
requiresDocument
chosen
Indicates that one entity can only proceed, be valid, or be completed if a specified document is provided or present.
-
B.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requiredInformation
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
E.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 27, 2026, 3 p.m.