Triple
T199146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Motor Credit Company |
E4062
|
entity |
| Predicate | regulatesUnder |
P1313
|
FINISHED |
| Object | U.S. financial regulations |
—
|
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: U.S. financial regulations | Statement: [Ford Motor Credit Company, regulatesUnder, U.S. financial regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesUnder Context triple: [Ford Motor Credit Company, regulatesUnder, U.S. financial regulations]
-
A.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
B.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
C.
regulatesParticipationIn
Indicates that one entity controls, directs, or sets rules governing another entity’s involvement in an activity, process, or system.
-
D.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcc6dc88190b8c24b485588dfe4 |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.