Triple
T33033480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Act 1955 |
E845236
|
entity |
| Predicate | wasConsolidatedBy |
P77053
|
FINISHED |
| Object | Armed Forces Act 2006 |
—
|
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: Armed Forces Act 2006 | Statement: [Army Act 1955, wasConsolidatedBy, Armed Forces Act 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasConsolidatedBy Context triple: [Army Act 1955, wasConsolidatedBy, Armed Forces Act 2006]
-
A.
consolidatedBy
chosen
Indicates that one entity has been merged, unified, or combined into a more cohesive whole by another entity.
-
B.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
C.
consolidatedUnder
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
-
D.
consolidatedAfter
Indicates that one entity was formed or unified as a result of merging or combining multiple entities after a specified point in time.
-
E.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.