Triple
T29603917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organic Law 6/2006 |
E754524
|
entity |
| Predicate | BOENumber |
P167499
|
FINISHED |
| Object | 172/2006 |
—
|
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: 172/2006 | Statement: [Organic Law 6/2006, BOENumber, 172/2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BOENumber Context triple: [Organic Law 6/2006, BOENumber, 172/2006]
-
A.
BDNumber
Indicates that an entity is associated with a specific BD (Business Development or similar domain-specific) identification number used to uniquely reference it.
-
B.
orderNumber
Indicates the unique identifier assigned to a specific order within a transaction or ordering process.
-
C.
BOIC
Indicates a relationship where one entity is the beneficiary or intended recipient of an item, action, or outcome provided or directed by another entity.
-
D.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
E.
boonDetails
Indicates the specific terms, conditions, or characteristics associated with a granted benefit or favor within the relationship or action.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de5e2b88190bd2529cc77629609 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:24 p.m.