Triple
T32414730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table API |
E828308
|
entity |
| Predicate | isSchema |
P174053
|
FINISHED |
| Object | schema-less |
—
|
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: schema-less | Statement: [Table API, isSchema, schema-less]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSchema Context triple: [Table API, isSchema, schema-less]
-
A.
isInfiniteSchema
Indicates that a schema has no finite bounds, allowing for an unbounded or limitless structure or set of elements.
-
B.
hasSchemaLanguage
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
-
C.
hasAxiomSchema
Indicates that one entity is associated with, defined by, or governed through a particular axiom schema.
-
D.
schemaName
Indicates that an entity is associated with a particular schema by specifying the name of that schema.
-
E.
isStruct
Indicates that an entity is a structured data type (such as a struct) rather than a primitive or other kind of type.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c25bb38881909a5a0552b316e970 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:53 a.m.