Triple
T17718048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FCC Form 486 |
E442256
|
entity |
| Predicate | mustReference |
P116941
|
FINISHED |
| Object | funding request numbers |
—
|
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: funding request numbers | Statement: [FCC Form 486, mustReference, funding request numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustReference Context triple: [FCC Form 486, mustReference, funding request numbers]
-
A.
requiresReferent
chosen
Indicates that one entity depends on or must reference another specific entity in order to be valid, interpretable, or complete.
-
B.
mustTouch
Indicates that the entities are required to be in direct physical contact with each other.
-
C.
mustDeclare
Indicates that one entity is required or obligated to formally state, disclose, or announce something to another entity or authority.
-
D.
mustEstablish
Indicates that one entity is obligated or required to create, set up, or formally establish another entity, condition, or relationship.
-
E.
mustRetain
Indicates that an entity is required to keep or preserve another entity and is not allowed to discard, delete, or release it.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e474834aec81909ab7e8224c5a39d7 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.