Triple
T6273810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unbound Gravel |
E140602
|
entity |
| Predicate | supportRules |
P69096
|
FINISHED |
| Object | limited outside support |
—
|
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 outside support | Statement: [Unbound Gravel, supportRules, limited outside support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportRules Context triple: [Unbound Gravel, supportRules, limited outside support]
-
A.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
B.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
supportsRegulation
Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
-
D.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063be5a148190a8752426d2d220f8 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:25 p.m.