Triple
T11897511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOA |
E283072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formal agreement document |
C3153
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: formal agreement document Context triple: [LOA, instanceOf, formal agreement document]
-
A.
legal agreement
chosen
A legal agreement is a formally recognized arrangement between two or more parties that creates enforceable rights and obligations under the law.
-
B.
concluding document
A concluding document is a final written record that summarizes outcomes, decisions, and next steps at the end of a process, project, or agreement.
-
C.
GAC document
A GAC document is an official record or report produced by a General Assembly Committee (GAC) that outlines its decisions, recommendations, proceedings, or policies.
-
D.
fictional legal document
A fictional legal document is an invented text that mimics the structure, language, and authority of real legal instruments (such as contracts, statutes, or court opinions) for use within a narrative, game, or speculative scenario.
-
E.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
- F. None of above.
Provenance (1 batch)
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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.