Triple
T14990809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLC |
E373829
|
entity |
| Predicate | commonFormationDocument |
P27217
|
FINISHED |
| Object | articles of organization |
—
|
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: articles of organization | Statement: [LLC, commonFormationDocument, articles of organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonFormationDocument Context triple: [LLC, commonFormationDocument, articles of organization]
-
A.
officeFormation
Indicates the event or process by which an office or official position is created, established, or formally constituted.
-
B.
documentForm
chosen
Indicates the specific format or structural type in which a document is presented or recorded.
-
C.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
D.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
E.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded715db408190b44e8a8452c79764 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.