Triple
T36977612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Other Dependent Credit |
E914741
|
entity |
| Predicate | requiresDependentToMeet |
P201696
|
FINISHED |
| Object | support test |
—
|
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: support test | Statement: [Other Dependent Credit, requiresDependentToMeet, support test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDependentToMeet Context triple: [Other Dependent Credit, requiresDependentToMeet, support test]
-
A.
requiresDependentNotTo
Indicates that one entity imposes a constraint that another dependent entity must refrain from performing a specific action or behavior.
-
B.
requiresDependentToHave
chosen
Indicates that one entity’s validity or operation is contingent on another entity possessing a specified attribute, state, or condition.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
E.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:14 p.m.