Triple
T18786081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langmuir monolayers |
E459378
|
entity |
| Predicate | areSpreadOn |
P133009
|
FINISHED |
| Object | liquid subphase |
—
|
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: liquid subphase | Statement: [Langmuir monolayers, areSpreadOn, liquid subphase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areSpreadOn Context triple: [Langmuir monolayers, areSpreadOn, liquid subphase]
-
A.
spreadsAs
Indicates that one entity propagates, extends, or disseminates from another entity or source.
-
B.
spreadBy
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
C.
spreadTo
Indicates that something extends, propagates, or is transmitted from one entity, location, or context to another.
-
D.
isBroad
Indicates that something has a large width or extensive scope relative to a reference or context.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978154ac819096356d2a488b45f0 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.