Triple
T26046532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act XVIII of 1887 |
E647846
|
entity |
| Predicate | typeOfActNumbering |
P3378
|
FINISHED |
| Object | Act XVIII of 1887 |
—
|
NE NERFINISHED |
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: Act XVIII of 1887 | Statement: [Act XVIII of 1887, typeOfActNumbering, Act XVIII of 1887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfActNumbering Context triple: [Act XVIII of 1887, typeOfActNumbering, Act XVIII of 1887]
-
A.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
B.
legalNumbering
Indicates that an entity has an officially assigned legal or regulatory identification number.
-
C.
categoryNumbering
Indicates that items within a category are assigned an ordered or structured numbering scheme that defines their position or sequence in that category.
-
D.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
E.
standardNumberingScheme
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 22, 2026, 9:10 a.m.