Triple
T20240756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana Separate Car Act |
E498280
|
entity |
| Predicate | testCase |
P139365
|
FINISHED |
| Object | Homer Plessy’s arrest in 1892 |
—
|
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: Homer Plessy’s arrest in 1892 | Statement: [Louisiana Separate Car Act, testCase, Homer Plessy’s arrest in 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testCase Context triple: [Louisiana Separate Car Act, testCase, Homer Plessy’s arrest in 1892]
-
A.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
B.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
C.
testingMethod
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
-
D.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
E.
testedInCase
Indicates that something (such as a method, component, or behavior) is exercised or verified within a particular test case.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716eabf48190ae4e760f472114bd |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.