Triple
T21295732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael E. Hurley |
E524915
|
entity |
| Predicate | hasDocumentedPublicInformation |
P39118
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Michael E. Hurley, hasDocumentedPublicInformation, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentedPublicInformation Context triple: [Michael E. Hurley, hasDocumentedPublicInformation, limited]
-
A.
hasNotableDocument
Indicates that an entity is associated with a document that is considered significant, noteworthy, or of particular importance.
-
B.
hasDocumentationStatus
chosen
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
C.
hasDOC
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
-
D.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
E.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385858ec8190bdc9c5cdcb8d4507 |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:04 p.m.