Triple
T31741709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Architects Act, 1972 |
E810158
|
entity |
| Predicate | protectsTitle |
P13930
|
FINISHED |
| Object | Architect |
—
|
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: Architect | Statement: [Architects Act, 1972, protectsTitle, Architect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsTitle Context triple: [Architects Act, 1972, protectsTitle, Architect]
-
A.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
B.
securedTitleAfterMatch
Indicates that an entity successfully obtained or clinched a title as a direct result of the outcome of a specific match.
-
C.
isTitleDefenseFor
Indicates that an event, match, or competition serves as the defending champion’s attempt to retain an existing title or championship.
-
D.
protectsRight
chosen
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 30, 2026, 11:25 p.m.