Triple
T8888888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John O. Power |
E211610
|
entity |
| Predicate | publicInformationAvailability |
P25763
|
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: [John O. Power, publicInformationAvailability, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicInformationAvailability Context triple: [John O. Power, publicInformationAvailability, limited]
-
A.
publicDetailsAvailability
chosen
Indicates whether and to what extent certain details or information are accessible to the general public.
-
B.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
C.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
D.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
E.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618f94108190b03248832bfe68a9 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.