Triple
T35790727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tic Tac (UFO) |
E1034684
|
entity |
| Predicate | sizeDescribedAs |
P28652
|
FINISHED |
| Object | about 40 feet long |
—
|
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: about 40 feet long | Statement: [Tic Tac (UFO), sizeDescribedAs, about 40 feet long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeDescribedAs Context triple: [Tic Tac (UFO), sizeDescribedAs, about 40 feet long]
-
A.
sizeDescription
chosen
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
B.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
C.
sizeType
Indicates the kind or category of size associated with an entity, such as relative scale, measurement type, or size classification.
-
D.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
-
E.
weightSize
Indicates a relationship between an entity’s weight and its physical size, typically expressing how one varies or is characterized in terms of the other.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22e0ff88190989a5df84fca968b |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.