Triple
T20023602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Tucker Act |
E494920
|
entity |
| Predicate | allowsSuitBy |
P273
|
FINISHED |
| Object | private parties |
—
|
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: private parties | Statement: [Little Tucker Act, allowsSuitBy, private parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsSuitBy Context triple: [Little Tucker Act, allowsSuitBy, private parties]
-
A.
hasSuit
Indicates that an entity possesses, wears, or is associated with a particular suit (such as clothing, armor, or a formal outfit).
-
B.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
C.
lessSuitableFor
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
-
D.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
suit
Indicates that one entity is appropriate, fitting, or satisfactory for another entity or a particular purpose or situation.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628a1ecc8190bf6ee0bedb61e0b8 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.