Triple
T35475460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY FOIL |
E1025318
|
entity |
| Predicate | appliesToRequesters |
P199588
|
FINISHED |
| Object | any person |
—
|
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: any person | Statement: [NY FOIL, appliesToRequesters, any person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToRequesters Context triple: [NY FOIL, appliesToRequesters, any person]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
requiresApplicationTo
Indicates that one entity can only access, use, or obtain another entity if a formal application or request process is completed.
-
C.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
D.
mayBeRequestedIn
Indicates that one entity is allowed or eligible to be requested within the context or scope of another entity.
-
E.
appliesAlsoTo
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
- F. None of above. chosen
Provenance (4 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69ff46aefe248190a80d898df6ef1340 |
completed | May 9, 2026, 2:37 p.m. |
Created at: May 3, 2026, 4:04 p.m.